[11:04] <sadleder> hi all, maybe not especially related to upstart, but does anyone know a preferred way to temporarily disable shutdown of a system
[11:05] <sadleder> i mean a scenario in which a system is administered remotely, but has local users
[01:32] <root____> Hello all, I searched all over and im probably just plain stupid. I dont have an implentetion in fron of me but trying to figure out how upstart gets the default run level.. should i still use inittab?
[01:37] <root____> nm i figured it out ithink.. just have to get used to events.. if i still want runleves ill do a event on startup and define runlevels in that and other events based on that.. take care and an ty
[03:00] <cryptom> hi all, is there an "automated way" to improve startup time with upstart? I've upgraded from dapper to edgy and seem to have much longer boot times.
[05:12] <Seveas> cryptom, improving startup time isn't a goal of upstart
[05:13] <psibox> do you know how i can find out the order in which the startups have been called ?
[05:13] <psibox> i have a problem that an nfs-mounted fs does not appear in /etc/mtab
[05:14] <psibox> then updatedb does not detect that it's NFS and indexes 2TB. from all clients.
[05:51] <cryptom> Seveas, oh, really, then I must have misunderstood something I read on the net (or mixed it up with something else). I just thought that a new startup system could only be faster (starting services in parallel, not serial)
[05:52] <cryptom> than the old-fashioned sysvinit
[05:52] <Seveas> cryptom, a side effect of a fully upstart-ized init system willprobably a significant improvement in startup time
[05:52] <Seveas> however, it is not a goal
[05:53] <Seveas> and in ubuntu edgy, upstart is not used to its full potential, the only startup time improvements come from the dash-as-/bin/sh change
[05:53] <cryptom> Seveas, I understand that, I think the goal is to still have control once the services are started
[05:53] <cryptom> and not just "fire and forget"
[05:54] <cryptom> Seveas, dash-as-/bin/sh ?
[05:54] <maro> cryptom: /bin/sh -> /bin/dash
[05:54] <Seveas> cryptom, the primary goal was to get rid of all horrible race conditions in init
[05:54] <maro> (instead of bash)
[05:54] <Seveas> the goal now seems to be "to take over the world"
[05:55] <maro> Seveas: no scm action in the past 2 weeks though, seems to have stalled :)
[05:55] <cryptom> ;-)
[05:55] <Seveas> maro, LOL
[05:55] <Seveas> they've been very busy designing th beast
[05:55] <Seveas> lots of goodness is coming up
[05:59] <cryptom> Seveas, ok, thanks for the clarification
[06:21] <psibox> how can i turn on some kind of debug info for upstart ?
[06:21] <psibox> is there anything in place ?
[06:36] <Keybuk> psibox: boot with --debug as a kernel option
[06:37] <psibox> thanks, will try that.
[06:38] <psibox> after boot i'm missing NFS filesystems in /etc/mtab. /proc/mounts is ok, fs is mounted, but /etc/mtab ist wrong.
[07:23] <Keybuk> oh, that's just a usual ubuntu bug
[07:27] <psibox> well, that's pretty bad.
[07:27] <psibox> is there a fix ?
[07:27] <psibox> what's causing this ?
[07:47] <maro> Keybuk: busybox claims /etc/mtab is obsolete and should be a symlink to /proc/mounts on "modern distros" - do you know why that isn't the case on ubuntu?
[07:54] <psibox> maro: interesting. i read somewhere (can't find it right now) that linking /etc/mtab to /proc/mounts was a bad idea. unfortunately the poster didn't explain why
[08:05] <Seveas> that would make /etc/mtab unusable before /proc is mounted. Not sure if that matters though
[08:06] <Keybuk> there are mount options in /etc/mtab that do not appear in /proc/mounts
[08:30] <psibox> like 'noquota'. this breaks (kind of) quota.
[08:39] <obenbohne> hi Seveas!
[10:41] <obenbohne> hi Seveas
[12:14] <Keybuk> wasabi: around?