| imop45 | hi all, I have a q that someome might be able to answer. | 00:08 |
|---|---|---|
| imop45 | I have a Palm WebOS device that uses upstart | 00:09 |
| imop45 | currently upstart just uses a graphic boot screen. | 00:09 |
| imop45 | I was wondering if a Verbose Mode would be possible. | 00:10 |
| imop45 | I've been searching the upstart site to see how to enable a verbose mode but can't seem to find it. | 00:12 |
| imop45 | hmm, so webOS uses a splash program | 00:16 |
| imop45 | are upsplash and splashy the only 2? | 00:17 |
| JanC | normally upstart jobs are in /etc/init/ (new versions) or /etc/event.d/ (older versions) | 00:25 |
| JanC | so I guess you should find it there somewhere (if it's started by upstart at all) | 00:26 |
| corecode_ | what do you mean with new/old versions? | 10:56 |
| corecode_ | ah! | 11:58 |
| corecode_ | how can i start a binary that doesn't daemonize? | 11:59 |
| corecode_ | i'm sorry to say so, but upstart is horribly underdocumented | 12:16 |
| corecode_ | i just can not find any documentation on how to start a non-backgrounding service | 12:16 |
| ion | programname.conf: exec programname | 12:21 |
| ion | start programname | 12:21 |
| corecode_ | that's what i have | 12:21 |
| corecode_ | but it just does not return | 12:21 |
| corecode_ | the start command | 12:21 |
| ion | Anything interesting in syslog? | 12:22 |
| corecode_ | the service gets started, sure | 12:22 |
| corecode_ | but start doesn't return | 12:22 |
| ion | Oh. I take it you have an ancient version of Upstart? In that case, add the line ‘service’ to the config. | 12:23 |
| corecode_ | i don't know which version is running | 12:24 |
| ion | In old versions of Upstart, ‘task’ was the default. Nowadays, ‘service’. A job being a task means that ‘start job’ returns when the program exits (i.e. the task is finished). | 12:24 |
| corecode_ | ah | 12:28 |
| corecode_ | ok | 12:28 |
| corecode_ | yea, too bad that this is not documented | 12:28 |
| ion | Current Upstart releases have much better documentation than the ancient ones. | 12:36 |
| corecode_ | still it is confusing, and barely non-existing on the web | 12:36 |
| corecode_ | thanks for your help | 12:43 |
| ion | It’s in the form of man pages that come with the package. | 12:45 |
| corecode_ | yes i know | 12:47 |
| corecode_ | but on my platform | 12:47 |
| corecode_ | man 5 init = fail | 12:47 |
| imop45 | hi could someone guide me in enabling verbose boot mode on upstart? | 17:28 |
| imop45 | I'm trying to get a WebOS to boot without a splash screen. | 17:29 |
| === pocek_ is now known as pocek | ||
| zdzichuBG | Hi, "--debug" in kernel comand line is supposed to dump all events emitted. Where can I read those logs? | 18:41 |
| ion | Upstart outputs them to syslog, and until a syslogd is available, they’ll only go to the console. A proper boot logger is in TODO. | 18:46 |
| zdzichuBG | Thanks. | 18:50 |
| zdzichuBG | This is not good for me, unfortunately. I'm trying to debug problem where my application do not start on event which should be emitted, according to upstart documentation. I believe event is somehow not emitted. | 18:51 |
| zdzichuBG | I have | 18:52 |
| zdzichuBG | start on device-added SUBSYSTEM=block DEVNAME=sd[ab][!0-9] | 18:52 |
| ion | [!0-9]? | 18:57 |
| zdzichuBG | yes, I'm only interested in whole devices, not partitions | 19:06 |
| ion | sd[ab][!0-9] matches e.g. sdaq, sdb! and sda_ but not sda or sdb. You’ll want sd[ab] | 19:08 |
| zdzichuBG | uhm, isn't empty string part of [!0-9] ? | 19:11 |
| ion | See glob(7) | 19:13 |
| zdzichuBG | OK, thanks. Apparently I screwed the rule again (the one I had in F12 was wrong, also) :) | 19:15 |
| === sadmac2__ is now known as sadmac2 | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!