[02:56] Is it because upstart gets confused when it's not PID 1 that Ubuntu's bootchart starts within initramfs (rather than with init=/sbin/bootchartd)? [05:07] twb: no, it's useful to factor in the time spent in initramfs too [05:07] initramfs runs before init? [05:07] twb: as we found a few weeks ago, for example, one developer's laptop spends nearly half its bootup in initramfs [05:07] twb: correct. initramfs runs before / is even mounted, much less an init daemon exists [05:07] You're right, I was confused [05:44] hello twb [05:45] I am VERY interested in profiling the bootsequence, die you get bootchart runnning? [05:49] keesj: I have it running on Debian Lenny... [06:02] and that uses upstart? [06:03] let me put it differently , can i "bootchart" upstart? [06:16] keesj: that's broadly my question. [06:43] twb: My feeling is no. [08:06] keesj: i don't see why not, you just have to start it in initramfs and have a stop task at the end of boot [08:06] keesj: jdong's upstart scripts for ubuntu work with bootchart [08:09] you can bootchart upstart with native scripts in the normal way you would start bootchart (init=/path/to/bootchart on kernel command line), i've done it [08:11] AlexExtreme: but then you don't chart initramfs time [08:11] mmm, true [08:12] which for me is 10 seconds of a 32 second boot :P [08:12] if you're using it with initramfs you don't need to have a stop task for it, bootchart will stop in it's normal way [08:12] hehe [08:12] i wasn't using initramfs with mine though [08:12] no, you still need a stop task [08:13] really? why wouldn't the way bootchart stops itself work? [08:13] me and jdong found that out when i got a 12 minute bootchart that took 10 minutes to convert from svg to png :P [08:13] it waits until gdm, kdm, xdm or getty starts [08:13] mmm... :P [08:14] http://www.realistanew.com/random/hardy-20080317-3.png <--initramfs time is important to measure :P [08:14] mm, yeah [08:15] after that boot we spent awhile trying to maximize disk throughput throughout the process as you can see it seeking most of the time there [08:15] http://alex-smith.me.uk/files/bootchart-ud.png << insane boot time using upstart native scripts on a custom (LFS based) distro with a custom kernel ;) [08:16] ended up with a boot that has a more consistent throughput but a lower max throughput and thus takes the same amount of time to boot :P [08:16] wow [08:16] except you don't start anything :P [08:17] would still take my system 13 seconds or so though, since 10 seconds is lost in initramfs :P [08:17] well, it booted up to a getty with networking enabled [08:17] yeah [08:17] http://alex-smith.me.uk/files/bootcharts/bootchart-upstart3.png << that's a better one from when I was getting upstart on frugalware, which doesn't use initramfs [08:18] so stick about 10 secs on for initramfs and you a bit less than your bootchart [08:18] *get a [08:18] that's a weird chart [08:18] your high disk usage was at the end of boot [08:19] about where gdm starts [08:19] http://www.realistanew.com/random/hardy-20080317-10.png [08:19] that boot is with readahead disabled and i still peak at beginning [08:19] probably something screwed up that i've done then :p [08:20] also i seem to start about 3x as many things :P [08:20] pff, i like my simplicity ;) [08:21] i suspect i can get this thing down to 20 seconds easily if i fix my initramfs problems and get rid of stuff i don't use from startup [08:21] which is really exciting because with sysvinit 45 seconds was crazy fast :P [08:22] with sysv on that system i was getting 29 seconds [14:28] hi. how do i handle a package that's removed but not purged? [15:14] tv: This is #upstart, btw. :-) [15:40] yeah i mean it's event.d [15:40] i don't want to keep respawning on exec /usr/bin/does-not-exist-anymore [16:07] Well, you could always purge the package. ;-) [19:07] thanks for the help guys . i was not able to read earlyer