[01:37] 'status JOB' exists with 0 when the job is running and when it isn't. is there a way to tell from an exit code if a job is running with upstart (since starting now emits 1 if it is already running)? === ev1 is now known as ev === Ng_ is now known as Ng === notting__ is now known as notting [19:42] is there a way to reset the upstart respawn counter? [19:42] with inittab, the init q command does this [19:52] dchen_: same [21:13] Keybuk: init q didn't seem to do it [21:13] I just waited for the timeout [21:18] oh, no, it's running [21:20] pardon? [21:27] you need to stop and start the job [21:27] (with the telinit in between) [21:29] hrm [21:29] so I tried [21:29] initctl stop blah [21:29] init q [21:30] initctl start blah [21:30] and it had an error message that it was restarting too fast or something [21:31] Keybuk: you said ubuntu doesn't re-exec init on every glibc change, but instead does it just before unmounting the FS? [21:33] hi, has anyone tried to cross compile upstart 0.63 yet? [21:34] asalkeld: yes. there's been some complaints about the dependency on libnih creating issues [21:34] It has problems as nil-dbus-tool is build with the cross CC [21:35] asalkeld: yep [21:35] asalkeld: don't know that there's been a resolution sadly [21:35] does nil-dbus-tool generate c files (only - no other function?) [21:36] if so , it would be good if these c files could be generated as part of the shipped tarball [21:37] so we would not have to compile nil-dbus-tool at all. [21:37] asalkeld: interesting idea. [21:37] ok, well thanks - I'll try find a solution myself [21:38] asalkeld: technically the c files are not "source," but rather the xml they are generated from is [21:38] like a configure file ... [21:38] true. [21:39] often there is some prep that is done before distributing a release (changelog, autotools, etc...) [21:40] this could be a part of this [21:40] unless there is some dbus version dependant code. [21:41] sadmac: correct [21:41] wing-commander scott% grep telinit /etc/init.d/umountroot [21:41] [ -f /var/run/init.upgraded ] && telinit u || : [21:41] Keybuk: why re-exec at all? From a vm perspective I don't see what problems it causes. [21:42] sadmac: if you've upgraded libc or init, you have a file open on the root filesystem that is "dirty" [21:42] so you cannot remount readonly [21:42] the remount will fail [21:42] and you'll power off a dirty root [21:42] incur a mandatory fsck on reboot [21:42] etc. [21:42] dunno why its dirty [21:42] dirty implies there's an alternate "clean" state [21:43] yes [21:43] there's no laundering procedure for the pages in question [21:43] they should just be freed [21:43] or rather become anonymous [21:44] they don't [21:44] kernel mis-step methinks (or posix mandating stupidity as is often the case) [21:48] like most stupidity, posix [21:48] fantastic [21:57] My vbox init scripts work. Yay.