=== j_ack [n=rudi@p508D8468.dip0.t-ipconnect.de] has joined #upstart === wasabi [n=wasabi@ubuntu/member/wasabi] has joined #upstart === j_ack [n=rudi@p508D8468.dip0.t-ipconnect.de] has joined #upstart === gepatino [n=gabriel@200.123.178.117] has joined #upstart === Starting logfile irclogs/upstart.log === ubuntulog [i=ubuntulo@ubuntu/bot/ubuntulog] has joined #upstart === Topic for #upstart: Upstart 0.3.8 | http://upstart.ubuntu.com/ | http://upstart.ubuntu.com/wiki/UpstartOnGentoo === Topic (#upstart): set by Keybuk at Fri Mar 16 18:29:42 2007 === int0x0c [n=ben@161.253.46.72] has joined #upstart === sadleder [n=sadleder@p5081257C.dip0.t-ipconnect.de] has joined #upstart === nenolod_ [n=nenolod@ip70-189-74-69.ok.ok.cox.net] has joined #upstart === Md [i=md@freenode/staff/md] has joined #upstart === sadlede1 [n=sadleder@p50812330.dip0.t-ipconnect.de] has joined #upstart === Keybuk [n=scott@quest.netsplit.com] has joined #upstart === mbiebl [n=michael@e180106193.adsl.alicedsl.de] has joined #upstart === AlexExtreme [n=AlexExtr@frugalware/developer/AlexExtreme] has joined #upstart === mbiebl [n=michael@e180106193.adsl.alicedsl.de] has joined #upstart [12:40] mbiebl: hi, how are you planning to integrate replacement-initscripts into debian when they get used in ubuntu? [12:40] sure, I'm already working on them ;-) [12:41] sorry, but I have to run now... [12:41] cu later [01:45] about interaction with user.... why would anyone want to do that during boot? [01:45] retrieving keys for encrypted filesystems [01:45] (or Apache SSL passphrases) [01:45] driving fsck responses [01:46] why not provide that on the boot command line? [01:46] I wouldn't want my bootup to halt on some stupid question... [01:47] guess you could define some base services that shouldn't ask any question to get around that though. [01:50] some people do want their boot to halt though [01:50] though heres a thought ... pre-seeding answers to questions ;p [01:50] <_ion> "Yo Linux! If something in the boot asks whether i want to fix inode 46837, the answer is yes." [01:51] or "just fix every damned fsck thing" [01:51] (who doesn't hold down the "Y" key until fsck goes away? :p) [01:51] "no, actually, I don't want to fix my filesystem) [01:51] <_ion> I *always* set FSCKFIX=yes [01:52] <_ion> If we were evil enough, we could use libwhat to let the user input her login and password before gdm is started. :-) [01:56] seems like you're on the same track as me.... you don't want questions during bootup. ;P [01:56] "just do the right thing" :) [02:03] encrypted partitions might be a separate issue.... still I'd rather have the answer provided from the start and no questions asked... (or extend grub to ask questions if something more "user friendly" is needed. I guess grub could even be smart about it... grub reads filesystems already, no? Could check /etc/fstab on the fly if any key is needed... or if the root partition needs would know that as well when trying to access it?) [02:04] not sure about apache / ssl-keys ... why would you want to auto-start something that can't be auto-started? [02:08] _ion: or just start gdm on a framebuffer ;-) [02:14] gdm takes ages to start [02:18] Keybuk: sure, just kidding [02:24] well, qingy is a framebuffer getty and it is themeable and whatnot [02:25] if you want a framebuffer screen for logging in this is much better than nihing your own [03:25] <_ion> fatal: If i were using an encrypted partition or apache with a password-protected SSL key, i'd definitely want to be queried for the passwords. [03:29] <_ion> keybuk: Btw, any new progress with the delayed watch stuff? [03:29] _ion: none, I have a half merge in my working branch [03:29] it's been a busy week [03:30] lots of CVs to read :-/ [03:30] <_ion> Alright. === tale_ [n=tale@199.26.183.1] has joined #upstart === mbiebl [n=michael@p54a38d29.dip0.t-ipconnect.de] has joined #upstart === j_ack [n=rudi@p508d857f.dip0.t-ipconnect.de] has joined #upstart [03:36] mbiebl: i found your upstart-jobs branch [03:37] hehe, that's not yet ready for public use though. [03:37] mbiebl: how are you going to push that into debian? will the jobs be in the indiviual packages? [03:37] That's my long term goal, yes. [03:38] mbiebl: sure, i'm just curious how the process will be [03:40] Short term, I will ship the upstart jobs for the most important packages myself. [03:40] Upon installation of the upstart-jobs package, I will scan which packages are currently installed, deactivate the sysv init script and activate the corresponding upstart job. [03:40] If I have a working set of native upstart jobs, I will start to ping the individual package maintainers and ask for them to include these files directly. [03:40] As I'm (co)-maintainer of dbus/hal/dhcdbd/network-manager I can do that for these packages directly. [03:41] (avahi-daemon too) [03:45] ok, so packages will provide both a sysv script and an upstart job [03:51] mbiebl: so i'm very much looking forward to using the first round of debian upstart-jobs [03:51] If you're willing to test them and give me feedback, that would be great. [03:52] do you run the jobs from upstart-jobs? [03:52] Maybe I have something working around mid next week. [03:53] http://pastebin.ca/406556 [03:54] So, basically the rc2.d/multiuser part is upstartified already. [03:56] wow! [03:56] btw, shouldn't avahi-daemon do the .local check from the sysvrc script? [03:56] policykit is not yet in debian, is it? [03:57] I'm currently packaging it for experimental while preparting hal-0.5.9 packages. [03:57] Its in the pkg-utopia svn [04:02] Something to wet your appetite: [04:02] http://debs.michaelbiebl.de/upstart/bootchart.png [04:06] oh dear! [04:11] around 15 sec the fully upstartified boot process kicks in. [04:11] oh yes, that point isn't hard to find ;-) [04:11] cu later [04:11] and the first part will be fast as well [04:11] ok, cu [04:45] can upstart detect docking events? === juergbi [n=juerg@80-219-17-102.dclient.hispeed.ch] has joined #upstart [05:03] tale_: was just about to reply to your e-mail ... :) [05:03] Upstart doesn't detect anything itself, it relies on things like udev, HAL, GNOME Power Manager, etc. to do all of the detection and handling [05:03] those processes request an upstart event be emitted through libupstart or the "initctl emit" tool [05:03] so provided you've got something already that can detect a docking event, it's just a matter of making it send an event to upstart [05:03] at which point upstart will start and stop services [05:03] the only events that upstart emits itself are "startup" and those due to jobs changing states [05:03] Keybuk, yeah I didn't notice the irc group until I had sent that email. [05:04] Keybuk, I'll do some more investigating to see how it is detected. I know it can be detected because there is a script that can be setup, but from what I hear it's not trival. This should work out of the box. === Starting logfile irclogs/upstart.log === ubuntulog [i=ubuntulo@ubuntu/bot/ubuntulog] has joined #upstart === Topic for #upstart: Upstart 0.3.8 | http://upstart.ubuntu.com/ | http://upstart.ubuntu.com/wiki/UpstartOnGentoo === Topic (#upstart): set by Keybuk at Fri Mar 16 18:29:42 2007 === sadlede1 [n=sadleder@p50812330.dip0.t-ipconnect.de] has left #upstart [] === sadlede1 [n=sadleder@p50812330.dip0.t-ipconnect.de] has joined #upstart === j_ack_ [n=rudi@p508d82dc.dip0.t-ipconnect.de] has joined #upstart === mbiebl [n=michael@e180127239.adsl.alicedsl.de] has joined #upstart === mbiebl [n=michael@e180127239.adsl.alicedsl.de] has joined #upstart [06:20] mbiebl, could you point me to your upstart jobs for debian sometime, i'd like to see what you're using there [06:21] brb, dinner [06:21] AlexExtreme: They are not ready yet. [06:21] i know, but what you have so far [06:22] Give me some more time until I feel confident to announce them. [06:42] Ok [07:26] mbiebl: thanks for uploading a new tracker with my patch :) [07:27] You're welcome. I have to thank for the patch. === int0x0c [n=ben@128.164.137.192] has joined #upstart [07:48] nice [07:48] syslog-ng doesn't write it's pid file when run with --foreground [08:07] AlexExtreme: Yeah, I used that too ;-) [08:07] :p [08:08] it was useful for my syslog-ng logrotate thing, but i'm writing a initctl pid command to replace that [08:09] argh, now I understood you. [08:12] AlexExtreme: what do you need the pid for? [08:12] postrotate [08:12] /bin/kill -HUP `cat /var/run/syslog-ng.pid 2>/dev/null` 2> /dev/null || true [08:12] endscript [08:12] that was what I had in the logrotate file for syslog-ng [08:12] That should imo be solved by providing a reload command [08:12] within upstart === Md_ [i=md@freenode/staff/md] has joined #upstart [08:12] h,, [08:12] *hmm [08:12] true [08:12] i'll file a bug report [08:12] Yes, please. [08:13] reload should probably use SIGHUP as default. [08:14] But there also should be the posssibilty to define a separate signal for reload [08:15] e.g. some daemons also use SIGUSR1 [08:15] ues [08:15] *yes === Md_ is now known as Md === Md [i=md@freenode/staff/md] has joined #upstart === phsdv [n=paul@dyn-83-156-72-252.ppp.tiscali.fr] has joined #upstart === sadlede1 [n=sadleder@p50812330.dip0.t-ipconnect.de] has left #upstart [] === mbiebl [n=michael@e180090208.adsl.alicedsl.de] has joined #upstart === j_ack [n=rudi@p508d82dc.dip0.t-ipconnect.de] has joined #upstart === int0x0c [n=ben@128.164.137.192] has joined #upstart