autofs does not stop when the system is halted

Bug #646694 reported by Daniel Lezcano
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
autofs (Ubuntu)
New
Low
Unassigned

Bug Description

Binary package hint: autofs

Ubuntu version:

Description: Ubuntu 10.04 LTS
Release: 10.04

Package version:

Architecture: amd64
Source: autofs5
Version: 5.0.4-3.1ubuntu5
Depends: autofs5

When the system halts, a signal is delivered to all the processes but automount does not receive it.

The sendsigs init script will build a list of processes to be omitted when sending a signal.
The omitted processes are the one not killed by the upstart jobs and the ones defined in the /lib/init/rw/sendsigs.omit.d/, /var/run/sendsigs.omit.

automount is not killed by upstart because the 'stop' action is not defined in /etc/init/autofs.conf, then it will belongs to the omitted processes list and therefore won't be killed.

In the normal use case, this is not visible because the shutdown will happens normally.
In the container context (lxc.sourceforge.net), it appears there are some remaining processes while the system is halted.

IMO, this is not the right behavior, the automount should receive a SIGTERM at shutdown time, this signal is catched and the daemon will do a proper shutdown. I was wondering if the autofs.conf script shouldn't have:

stop on runlevel [!2345]

Then the upstart job will deliver the sigterm signal to the process, and the automount will do its shutdown job normally.
It is cleaner for the system, and make it works for the container.

Mathias Gug (mathiaz)
Changed in autofs (Ubuntu):
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.