[pkg-wpa-devel] Correct shutdown ordering for wpa-ifupdown?

[Petter Reinholdtsen]

Hi.  What is the correct shutdown order for the wpa-ifupdown script?
Could its order during shutdown be the cause of the bugs #431966,
#477498 and #516733?

Its init.d header have this content:

### BEGIN INIT INFO
# Provides:             wpa-ifupdown
# Required-Start:       $network
# Required-Stop:        $network $remote_fs
# Should-Start:
# Should-Stop:
# Default-Start:
# Default-Stop:         0 6
### END INIT INFO

This is consistent with the update-rc.d call, but will lead to
problems if the wpa connection is needed when remote file systems are
to be umounted by umountnfs.

  update-rc.d wpa-ifupdown start 15 0 6 . >/dev/null || exit $?

Would it be better to change the dependencies to this, and move the
script a bit later in the shutdown sequence?  Why does it depend on
$remote_fs for shutdown?

### BEGIN INIT INFO
# Provides:             wpa-ifupdown
# Required-Start:       $network
# Required-Stop:        $network
# X-Stop-After:         umountnfs
# Default-Start:
# Default-Stop:         0 6
### END INIT INFO

The update-rc.d call should be changed like this if this ordering make
more sense:

  update-rc.d wpa-ifupdown start 32 0 6 . >/dev/null || exit $?

All this of course depend on the fact that the package register the
daemons in /lib/init/rw/sendsigs.omit.d/ to make sure the daemons are
not killed by sendsigs, which if I understand this correctly, was
implemented in version 0.6.2-1.

Happy hacking,
-- 
Petter Reinholdtsen