=== yankees26 [n=james@ool-182c6007.dyn.optonline.net] has joined #upstart === theCore [n=alex@modemcable128.255-131-66.mc.videotron.ca] has joined #upstart === yankees26 [n=james@ool-182c6007.dyn.optonline.net] has left #upstart [] === theCore [n=alex@modemcable128.255-131-66.mc.videotron.ca] has left #upstart ["Leaving"] === mbiebl [n=michael@e180079137.adsl.alicedsl.de] has joined #upstart === wasabi_ [n=wasabi@ubuntu/member/wasabi] has joined #upstart === Keybuk [i=scott@conference/canonical/x-1cb1ab998e7cc25b] has joined #upstart === mbiebl [n=michael@e180079137.adsl.alicedsl.de] has joined #upstart === Keybuk [i=scott@conference/canonical/x-6ce122786f7ed8ab] has joined #upstart === Keybuk [i=scott@conference/canonical/x-0dbeaf3a60177d47] has joined #upstart === sadleder [n=sadleder@p5081354A.dip0.t-ipconnect.de] has joined #upstart === Amaranth [n=travis@ubuntu/member/amaranth] has joined #upstart [11:04] hi all, maybe not especially related to upstart, but does anyone know a preferred way to temporarily disable shutdown of a system [11:05] i mean a scenario in which a system is administered remotely, but has local users === Md [i=md@freenode/staff/md] has joined #upstart === root____ [n=root@c-d60ce155.1567-1-64736c11.cust.bredbandsbolaget.se] has joined #upstart [01:32] 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] 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 === tonfa_ [n=tonfa@footwar.residence.ens-lyon.fr] has joined #upstart === cryptom [n=CrypTom@proxy.gymkirchenfeld.ch] has joined #upstart === mbiebl [n=michael@e180079137.adsl.alicedsl.de] has joined #upstart === tonfa_ is now known as tonfa [03:00] 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. === Amaranth [n=travis@ubuntu/member/amaranth] has joined #upstart === sadleder [n=sadleder@p5081354A.dip0.t-ipconnect.de] has left #upstart [] [05:12] cryptom, improving startup time isn't a goal of upstart [05:13] do you know how i can find out the order in which the startups have been called ? [05:13] i have a problem that an nfs-mounted fs does not appear in /etc/mtab [05:14] then updatedb does not detect that it's NFS and indexes 2TB. from all clients. [05:51] 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] than the old-fashioned sysvinit [05:52] cryptom, a side effect of a fully upstart-ized init system willprobably a significant improvement in startup time [05:52] however, it is not a goal [05:53] 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] Seveas, I understand that, I think the goal is to still have control once the services are started [05:53] and not just "fire and forget" [05:54] Seveas, dash-as-/bin/sh ? [05:54] cryptom: /bin/sh -> /bin/dash [05:54] cryptom, the primary goal was to get rid of all horrible race conditions in init [05:54] (instead of bash) [05:54] the goal now seems to be "to take over the world" [05:55] Seveas: no scm action in the past 2 weeks though, seems to have stalled :) [05:55] ;-) [05:55] maro, LOL [05:55] they've been very busy designing th beast [05:55] lots of goodness is coming up [05:59] Seveas, ok, thanks for the clarification === Keybuk [i=scott@conference/canonical/x-91239749e98da9ec] has joined #upstart [06:21] how can i turn on some kind of debug info for upstart ? [06:21] is there anything in place ? === phsdv [n=paul@83.152.234.106] has joined #upstart [06:36] psibox: boot with --debug as a kernel option [06:37] thanks, will try that. [06:38] after boot i'm missing NFS filesystems in /etc/mtab. /proc/mounts is ok, fs is mounted, but /etc/mtab ist wrong. [07:23] oh, that's just a usual ubuntu bug [07:27] well, that's pretty bad. [07:27] is there a fix ? [07:27] what's causing this ? [07:47] 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? === Md [i=md@freenode/staff/md] has joined #upstart [07:54] 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] that would make /etc/mtab unusable before /proc is mounted. Not sure if that matters though [08:06] there are mount options in /etc/mtab that do not appear in /proc/mounts [08:30] like 'noquota'. this breaks (kind of) quota. === obenbohne [n=obenbohn@adsl-68-88-212-155.dsl.rcsntx.swbell.net] has joined #upstart [08:39] hi Seveas! === yankees26 [n=yankees2@ool-182c6007.dyn.optonline.net] has joined #upstart === obenbohne [n=obenbohn@220.117.15.9] has joined #upstart [10:41] hi Seveas === theCore [n=alex@modemcable128.255-131-66.mc.videotron.ca] has joined #upstart === Keybuk [i=scott@conference/canonical/x-0b431b02b16f2a47] has joined #upstart === j_ack [n=rudi@p508D9BCE.dip0.t-ipconnect.de] has joined #upstart [12:14] wasabi: around? === ..[topic/#upstart:Keybuk] : Upstart 0.3.0 | http://upstart.ubuntu.com/ | http://upstart.ubuntu.com/doc/getting-started.html | http://upstart.ubuntu.com/wiki/ | irc logs: http://people.ubuntu.com/~fabbione/irclogs