Jaap Winius <jwin...@umrk.nl> writes: > Perhaps due to its LSB header, System V init (squeeze, v2.88dsf-11) ends > up giving the symlink for the /etc/init.d/openafs-fileserver script a > very low start sequence number, which starts it up too early. Since a > manual restart of this script soon after booting up never fails to start > it properly, I suggest that the start sequence number for its sysv-rc > symlinks be increased significantly. Using the update-rc.d script to > alter its sequence number seems not to work.
Boot sequencing in squeeze is now done via dependencies. Everything always starts as early as possible given the other services that it depends on, once those services have all been started. The AFS file server depends on: # Required-Start: $local_fs $remote_fs $network $time so yes, it will start fairly early. Clearly you feel that it should start after something else, since you're saying that it's starting too early, but you don't say what you mean by too early. Why is the start sequence too early? What isn't available that needs to be available for it to start? -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
