FS#12373 - [initscripts] Network filesystems are unmounted after the network itself has been shut down
Attached to Project:
Arch Linux
Opened by Olivier (litemotiv) - Sunday, 07 December 2008, 12:03 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 03 October 2009, 13:59 GMT
Opened by Olivier (litemotiv) - Sunday, 07 December 2008, 12:03 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 03 October 2009, 13:59 GMT
|
Details
Description:
On shutdown, (network) filesystems are unmounted after the network itself has been shut down, this results in a "umount.nfs: DNS resolution failed for xxx.xxx.xxx.xxx: Name or service not known" error thrown by netfs. Changing the order of deamons in rc.conf doesn't solve this. Additional info: * package version(s) 20081207-core * config and/or log files etc. Steps to reproduce: 1) mount a network filesystem (wireless in my case, don't know if eth0 produces different results) 2) shutdown or reboot, see terminal output |
This task depends upon
2) shutdown or reboot, see terminal output
Confirmed, eth0 produces the same result.
DAEMONS=(syslog-ng network portmap nfslock @netfs @crond @cups hal @cpufreq fam alsa @openntpd @mpd)
The problem also occurs when netfs isn't in the background.
[code]
DAEMONS=(syslog-ng @crond @net-profiles @portmap @nfslock @oss @hal @fuse @cpufreq)
[/code]
I agree with this though, that "leftovers" should be stopped first... anyone want to code it up? is we add a "in_array" function (with support for ignoring ! and @ prefixes), this should be much easier.
Additional point: If we remove the rc.shutdown check for the ! prefix, and just use the /var/run/daemons dir, we could do the exact same thing by adding it to the daemons array with !netfs. Shutdown will stop it in the right order if it is running.
http://projects.archlinux.org/?p=initscripts.git;a=commitdiff;h=7f1bd75ee6aaffddf47e704c46fbab5396b7dd19
Patch for it attached.