-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Petter,

On Sun, Jan 06, 2008 at 04:00:12PM +0100, Petter Reinholdtsen wrote:
>To be able to check boot script order, and also to be able to start
>boot scripts in parallel, it is important to know the dependencies of
>the various boot scripts.
[snip]
>I am working on a system to update the boot sequence based on these
>dependencies, and would like see this as the default in Lenny.


You mean insserv, right?

I have used indsserv for quite some time now without problems on a 
lessdisks-based thin client system (but not on servers or "fat" 
workstations yet).

>Here is a patch to document the dependencies.  I hope this is correct.

Thanks. They are a good start at least.


>+### BEGIN INIT INFO
>+# Provides:          netatalk
>+# Required-Start:    $remote_fs $syslog
>+# Required-Stop:     $remote_fs $syslog
>+# Default-Start:     2 3 4 5
>+# Default-Stop:      0 1 6
>+### END INIT INFO
> #
> # atalk         Netatalk 2.x initscript
> #
>
>As the stop script do not seem to do anything except killing the
>daemons, that task might be better left to the sendsigs script in
>runlevel 0 and 6.  If this is indeed the case, I recommend removing 0
>and 6 from the Default-Stop list.

Would you then suggest to also change the standard non-parallel 
installation to only sysv stop routine at level 1?


  - Jonas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHgRr2n7DbMsAkQLgRAmtPAJ9GghcyencgrIUxs52eEZso1hiGkQCeN/xY
jjFA0U9r5z2Lt4xsrTYKJgY=
=b91p
-----END PGP SIGNATURE-----



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to