FS#29624 - [initscripts] killall5 kills DHCP clients even if NETWORK_PERSIST="yes"

Attached to Project: Arch Linux
Opened by William Pettersson (SomeSwede) - Thursday, 26 April 2012, 13:17 GMT
Last edited by Dave Reisner (falconindy) - Monday, 30 April 2012, 09:56 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Tom Gundersen (tomegun)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: On systems with / (rootfs) mounted via network (like NFS), and where the network runs DHCP, shutting down and rebooting may fail. This happens when Arch gets to "Sending SIGTERM To Processes", and this step gets stuck in BUSY. This occurs because the dhcp client (in my case, dhcpcd) is sent a SIGTERM, and nicely releases the lease on the IP address it has. This causes a loss of network connectivity, the root filesystem no longer functions and the whole system appears to lock up.

I've fixed this on my end by adding a call to "add_omit_pids( $(pidof dhcpcd))" before the shutdown. This results in killall5 being passed an option telling it to not kill dhcpcd. As a net result, my system once again cleanly shuts down and reboots.

One reasonable fix would be to have /etc/rc.d/network also add $(pidof dhcpcd) to omit_pids if we are stopping network, and NETWORK_PERSIST="yes", but there are many other possible solutions as well.



Steps to reproduce:
Run a system that boots off NFS. Configure an IP address via DHCP. Attempt to shut down the machine.
This task depends upon

Closed by  Dave Reisner (falconindy)
Monday, 30 April 2012, 09:56 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#24898 
Comment by Matthias Dienstbier (fs4000) - Monday, 30 April 2012, 08:04 GMT
This should be related:  FS#24898 

Loading...