Hi Luca, 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.
> > 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. And why stop-bootlogd should not depend on bootchart?
Bootchart prints a message that bootlogd might want to capture. 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?
Bye, Jörg.
--
< Mr X.> jo: contact an admin to mount it for you
< jo> The admin is not, well how should I say it, he isn't very familiar with
the system. What should I tell my admin, what he should do?
< Mr X.> taking a sun solaris administration course.
signature.asc
Description: Digital signature http://en.wikipedia.org/wiki/OpenPGP
