[06:51] <kreign> hi, I'm trying to figure out what the upstart tool does on shutdown - eg. where the commands are defined that are run on shutdown
[06:52] <kreign> there's /etc/init for startup but I'm not seeing where eg. filesystems get umounted on shutdown
[11:15] <mbiebl> what distro?
[11:40] <djszapi> JanC there ?
[11:40] <djszapi> you tried last time to get the messages we discussed, can you remember ?
[11:41] <djszapi> KeyBuk told me it is because upstart cannot log to the kmsg and the proper daemons are not running during the boot-session to get those messages into the syslog.
[11:41] <djszapi> so I am trying to write a patch for upstart in order to be able to write into the kmsg for need.
[11:54] <djszapi> JanC: so it should fex. work after the startup.
[13:11] <SpamapS> kreign: shutdown happens on runlevel 0
[13:12] <SpamapS> kreign: most of it ist still handled in /etc/rc0.d
[13:12] <SpamapS> kreign: at least, in Ubuntu
[16:19] <gp5st> i'm here (http://upstart.ubuntu.com/index.html) where can i find a list of all directives for an upstart script? the wiki seems more technical and doesn't help:(
[16:20] <gp5st> but to the point, what i want to know is if there is respawn keyword, i've seen hints on other sites but i can't find one in the upstart page or man page
[16:29] <JanC> gp5st: read the init(5) manpage
[16:30] <gp5st> ah
[16:30] <gp5st> the (5) is what must have got me
[16:30] <gp5st> thanks:)
[16:30] <JanC> http://manpages.ubuntu.com/manpages/maverick/en/man5/init.5.html
[16:31] <gp5st> i found it, i was just doing man init before not man 5 init
[16:31] <gp5st> :)
[16:32] <JanC> there is a reference to init(5) at the bottom of init(8)  ;)
[16:33] <gp5st> i'm sure:)
[17:41] <kreignf> hi, I asked a question in here last night... does anyone know where the 'shutdown' time events are defined for upstart? eg. umount -a 
[20:20] <JanC> kreignf: depends on how you or your distro configures it
[20:21] <kreignf> JanC, :| ok, so where would I look? this is on ubuntu.
[20:21] <kreignf> JanC, I've dug around a bit but can not find anything suggestive (eg. grep umount /etc/init/*)
[20:22] <JanC> somebody answered that earlier today:
 kreign: shutdown happens on runlevel 0
 kreign: most of it ist still handled in /etc/rc0.d
 kreign: at least, in Ubuntu
[20:24] <kreignf> SpamapS, ah, thank you mate. ;P
[20:24] <kreignf> JanC, didn't see it, passed out before I got a response. thanks.
[20:25] <kreignf> not sure how i missed that on looking myself
[20:29] <SpamapS> kreignf: its not very obvious honestly
[20:29] <SpamapS> /etc/init/rc.conf covers it tho
[20:29] <kreignf> SpamapS, I'm not so sure I like the... complexity... of upstart, vs. classic init, at this point. at least for a server.
[20:30] <kreignf> SpamapS, seriously hope the intent is to have an all-in-one start/stop mechanism. 
[20:30] <SpamapS> kreignf: its the complexity of the hybrid implementation that makes most uneasy. As it gets more purely upstart.. it will seem more elegant. :)
[20:30] <kreignf> SpamapS, "sometimes it's set here and sometimes it's here" is not a good way to do it. :| 
[20:30] <kreignf> SpamapS, right. 
[20:30] <kreignf> SpamapS, I'm sure.
[20:31] <kreignf> still, I'd think startup and shutdown would be handled by upstart, at the least. you know, 'system' tasks.. not relegating umount to rc
[20:32] <SpamapS> I think that was the plan.. but the push in lucid was to get the bootup fast, not the shutdown. :)
[20:32] <kreignf> heh
[20:32] <SpamapS> and it actually works ok
[20:33] <kreignf> well I know where to stick my command then
[20:33] <kreignf> was kinda fading last night when I was looking into it
[20:33] <SpamapS> there is a need for some more synchronization .. there are races right now that can lead to the fs's not unmounting I'm afriad.
[20:33] <kreignf> not all cylinders were firing
[20:33] <kreignf> SpamapS, oh joy. :|
[20:33] <kreignf> SpamapS, where are the races?
[20:33] <kreignf> in upstart?
[20:33] <SpamapS> basically things that stop on runlevel [!2345] are not guaranteed to be stopped when fs's are unmounted
[20:34] <kreignf> ah
[20:34] <kreignf> eg. a long-terminating database process
[20:35]  * kreignf considers a lengthy sleep
[20:35] <kreignf> SpamapS, do the desktop guys push the ubuntu server direction quite a bit?
[20:35] <kreignf> ubuntu server is a nice thing
[20:35] <kreignf> (due to the newer kernel)
[20:36] <kreignf> just not sure i like the... process refinement?
[20:36] <kreignf> the resulting refinement is damn nice
[20:37] <SpamapS> kreignf: ubuntu is ubuntu .. server and desktop are just different "seeds"
[20:37] <SpamapS> kreignf: which affects the CD creation, and the length of security fixes.
[20:38] <kreignf> SpamapS, I don't recall sources.list having a definite "server" tag ; what determines the seed, to the mirror?
[20:38] <kreignf> or is it just a package selection that gets said support?
[20:38] <SpamapS> I would say.. realistically.. lucid is just now stabilized and tested enough that I'd want to roll something out on it.. 10.04.2 is out in a week or two.. it has a lot of little weird things fixed.
[20:39] <kreignf> SpamapS, yeah.
[20:39] <kreignf> SpamapS, been a bit long in the uptake IMO
[21:14] <kreignf> SpamapS, anything I can tell the kernel/upstart on boot to "tell me what you're doing!" ? I get "Starting /scripts/init-bottom... ; Done. Done. Finishing /scripts/init-bottom; Done - and then nothing
[21:14] <kreignf> just hangs there
[21:14] <kreignf> c-a-d reboots it
[21:14] <kreignf> but other 'n that I can't do much
[21:15] <SpamapS> kreignf: pass --verbose to the kernel
[21:16] <kreignf> SpamapS, hmm 
[21:19] <kreignf> SpamapS, would that be akin to "ro verbose" or do you mean --verbose?
[21:19] <SpamapS> kreignf: at the end of the line in grub, add --verbose
[21:19] <kreignf> SpamapS, the line starting linux, I presume
[21:20] <kreignf> just not familiar with --verbose as an ammendum to kernel boot opts
[21:20] <SpamapS> its unknown to the kernel, so the kernel passes it along to upstart
[21:20] <kreignf> ah ok.
[21:20] <kreignf> cool.
[21:50] <kreignf> SpamapS, I'm getting some cryptic "init: hostname goal/state is start/stopping post-stop->waiting/etc." info here, and then it just hangs up /goes no further after "init: handling stopped event"
[21:52] <kreignf> SpamapS, going to paste the image up
[21:54] <kreignf> SpamapS, mind if I email you the image?
[23:33] <SpamapS> kreignf: the lines before 'handling stopped event' are probably more interesting :)
[23:33] <SpamapS> kreignf: what OS is this?
[23:35] <kreignf> SpamapS, ubuntu
[23:35] <kreignf> 10.04
[23:35] <kreignf> LTS
[23:36] <kreignf> SpamapS, that was a couple hours ago; I got by it. now I'm trying to figure out why the freaking modules I need aren't loading on boot (they're in /etc/modules) but load just fiiine on manual modprobe
[23:37] <kreignf> heh
[23:37] <kreignf> and it works on another system :P
[23:40] <SpamapS> kreignf: /etc/init/module-init-tools.conf
[23:42] <kreignf> SpamapS, so this is going to sound a bit cheap but I see something scroll by on intial boot 'failed' - but I'm not finding it in logs. it's directly before login starts. 
[23:42] <kreignf> any idea where that'd be logged?
[23:42] <SpamapS> alt-f7
[23:42] <SpamapS> aka "the console"
[23:43] <kreignf> yey
[23:43] <kreignf> heh
[23:46] <kreignf> unfortunately it does not appear to scroll. meh.
[23:49] <SpamapS> kreignf: those should also end up in /var/log/boot.log
[23:49] <kreignf> yeah
[23:49] <kreignf> virtual console is slooow in vbox