Your message dated Wed, 26 Dec 2007 18:47:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#382410: fixed in sysvinit 2.86.ds1-43
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: sysv-rc
Version: 2.86.ds1-1

I had to read the init.d/rc script to make sure that
Knn* are _not_ called in reversed sort order. In facts,
the docs don't say it. Giving a single NN argument should
be deprecated. More misunderstandings below...

Related bugs: 268713, 288098
The following also applies to version 2.86.ds1-2, AFAICS.


Suggestions:

1) advertise update-rc.d
Add a paragraph in /etc/init.d/README saying something like

  Use the update-rc.d command to create symbolic links
  in the /etc/rc?.d as appropriate. See that man page
  for more details.

2) encourage setting the stop number correctly
In the man page I would replace

  this can be overridden by supplying one or two NN arguments

with

  this should be overridden if there are dependencies. For
  example if daemon B depends on A, then A must be started
  before B and B must be killed before A. You accomplish
  this by supplying two NN arguments. In general, core daemons
  should start early and be killed late, whilst applications
  can start late and be killed early. See EXAMPLES below.

  The first NN argument supplies the start sequence number and
  the second NN argument supplies the kill sequence number.
  Kill scripts are called first, passing a stop argument. Then
  start scripts are called passing a start argument. In either
  case, calls happen in ascending sequence number order.

  Supplying a single NN argument will use the same number for
  both start and kill links. This is supported for backward
  compatibility but is discouraged, as it may lead to inconsistent
  settings. As a rule of thumb, if you increase the start sequence
  number you should also decrease the stop sequence number, and
  vice-versa.

And then put more examples, e.g.

  Insert links at default runlevels when B requires A
     update-rc.d script_for_A defaults 80 20
     update-rc.d script_for_B defaults 90 10

  Insert a link to a service that (presumably) will not be
  needed by any other daemon
     update-rc.d top_level_app defaults 98 02

  Insert links for a script that requires services that
  start/stop at sequence number 20
     update-rc.d script_depends_on_svc20 defaults 21 19


Giving a single argument should be deprecated:

Let two independent daemons A and B configured in that way,
say A starts/stops at sequence number 20 and B at sequence
number 40. Then consider a service C that depends on A and
provides services necessary for B. (E.g. B can be configured
to do authentication using C.) Then C may start at 30, after
A but before B. There is no valid sequence number to stop C.
In facts, the stopping order should be kill-B, kill-C, kill-A,
which is not possible because A is killed before B.

Of course, such deadlocks may happen also letting the default 20,
but then at least it is clear that the problem hasn't been put. I
see no circumstance in which supplying `40' to the configuration
of B yields a benefit. What am I missing?


More misunderstandings:

- I have rc0.d/K21fam and rc3.d/S21fam. They used to be both at 20
  (see bug 280617.) What issue has been solved with that move?

- If anyone is registered there, please edit
  http://wiki.linuxquestions.org/wiki/Update-rc.d
  it says so:

    Yes, you can use the arguments start and stop, followed by NN
    (where NN are the desired runlevels) to specify which runlevels
    the script will start and stop in.




--- End Message ---
--- Begin Message ---
Source: sysvinit
Source-Version: 2.86.ds1-43

We believe that the bug you reported is fixed in the latest version of
sysvinit, which is due to be installed in the Debian FTP archive:

initscripts_2.86.ds1-43_i386.deb
  to pool/main/s/sysvinit/initscripts_2.86.ds1-43_i386.deb
sysv-rc_2.86.ds1-43_all.deb
  to pool/main/s/sysvinit/sysv-rc_2.86.ds1-43_all.deb
sysvinit-utils_2.86.ds1-43_i386.deb
  to pool/main/s/sysvinit/sysvinit-utils_2.86.ds1-43_i386.deb
sysvinit_2.86.ds1-43.diff.gz
  to pool/main/s/sysvinit/sysvinit_2.86.ds1-43.diff.gz
sysvinit_2.86.ds1-43.dsc
  to pool/main/s/sysvinit/sysvinit_2.86.ds1-43.dsc
sysvinit_2.86.ds1-43_i386.deb
  to pool/main/s/sysvinit/sysvinit_2.86.ds1-43_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Petter Reinholdtsen <[EMAIL PROTECTED]> (supplier of updated sysvinit package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


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

Format: 1.7
Date: Wed, 26 Dec 2007 19:36:43 +0100
Source: sysvinit
Binary: sysv-rc sysvinit-utils sysvinit initscripts
Architecture: source i386 all
Version: 2.86.ds1-43
Distribution: experimental
Urgency: low
Maintainer: Debian sysvinit maintainers 
<[email protected]>
Changed-By: Petter Reinholdtsen <[EMAIL PROTECTED]>
Description: 
 initscripts - Scripts for initializing and shutting down the system
 sysv-rc    - System-V-like runlevel change mechanism
 sysvinit   - System-V-like init utilities
 sysvinit-utils - System-V-like utilities
Closes: 382410 416223 457847
Changes: 
 sysvinit (2.86.ds1-43) experimental; urgency=low
 .
   * Fix typo in /etc/network/if-up.d/mountnfs fstab option parsing used to
     detect kerberos v5. (Closes: #416223)
   * Update sysv-rc documentation based on text and suggestions
     from Alessandro Vesely (Closes: #382410).
   * Modify rules to install /lib/init/bootclean with the execute flag
     set (Closes: 457847).
Files: 
 190c30f0f5a0107cdf4ef12a0d1e05cb 1037 admin required sysvinit_2.86.ds1-43.dsc
 262f26de5365aa778d556cb50da2423b 143868 admin required 
sysvinit_2.86.ds1-43.diff.gz
 9ef6c4b3029da84742f4a95d1c91c7e3 107638 admin required 
sysvinit_2.86.ds1-43_i386.deb
 9f8526fda741dbb153df217a987b3711 66584 admin required 
sysvinit-utils_2.86.ds1-43_i386.deb
 29b24664ca9ce944d64ce7d7d56d1726 62758 admin required 
initscripts_2.86.ds1-43_i386.deb
 5ca193e3a074b8f578a9636216d3d409 58078 admin required 
sysv-rc_2.86.ds1-43_all.deb

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

iD8DBQFHcp9720zMSyow1ykRAv53AJ4z0JHazB7q2vOOoNdhHXSASh9mHwCfYCgq
uBKqL5B2e5P6MVHNQGQmFUE=
=6Pbx
-----END PGP SIGNATURE-----



--- End Message ---
_______________________________________________
Pkg-sysvinit-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-sysvinit-devel

Reply via email to