Hi Jörg! On Fri, 22 Aug 2008 01:36:01 +0200, Jörg Sommer wrote: > Luca Capello schrieb am Wed 20. Aug, 14:10 (+0200): >> On Wed, 20 Aug 2008 12:45:11 +0200, Jörg Sommer wrote: >> > Luca Capello schrieb am Tue 19. Aug, 22:53 (+0200): >> >> According to [1], I'd say that bootchart is correct, since it should be >> >> started after rmnologin: >> >> >> >> # Required-Start: $remote_fs rmnologin >> > >> > I don't think so. >> >> I think you have missed my point, which is not at all related to bootchart. > > Okay. Yes, then I've didn't understood what you want me to do.
I'd like bootchart started (or, better, stopped) *after* the last "normal" script, since this is when the boot process is finished. >> > It's valid to place the rmnologin script earlier in the boot sequence, >> > if you use a graphical login. Then bootchart would stop to early. >> >> While rmnologin can be started before, this is not the case in a plain >> Debian installation. However, from my points above, we can assume that >> the last script is stop-bootlogd and not rmnologin, thus I'd say that >> bootchart should be started *after* stop-bootlogd. > > But from the logical POV, bootchart doesn't use any service provided by > stop-bootlogd. Fully ACK. > And why stop-bootlogd should not depend on bootchart? Bootchart > prints a message that bootlogd might want to capture. OK, let me explain how I see the bootchart process: bootchart records the boot process *without* modyfing my init script order. Because of that, I think it's clear that bootchart should be the first process to be started (this is always the case because it's called with the init=/ kernel argument) and the last to complete (i.e. the "start" init script). At least in the 99% of the cases and for sure for newbie users. Now, coming back to the stop-bootlogd dependency... While from a logical POV bootchart doesn't require stop-bootlogd to be started, *functionally* it does. Because since the LSB headers doesn't provide any mean to set the last script (something like $last, available only once) and since AFAIK stop-bootlogd is always available on a Debian system, we can assume that stop-bootlogd is the *last* script executed. Thus bootchart must be executed after stop-bootlogd. Yes, this is an ugly hack :-( > I think it's difficult to make a hard decision here. What I can do is > put a sleep into the init script. Did you discover that bootchart > stops to early? Actually I started using bootchart to measure the boot time for Debain on the Openmoko FreeRunner [1]. And after having installed bootchart I discovered this bug, whose consequences clearly stop bootchart to early if insserv is enabled. Thx, bye, Gismo / Luca Footnotes: [1] http://lists.linuxtogo.org/pipermail/smartphones-standards/2008-August/000269.html
pgpkyflJPdd17.pgp
Description: PGP signature
