Jeremy Fitzhardinge wrote:
>
> On 28-Mar-00 Morong, Gerry wrote:
> >
> > When I stop autofs and several users have mounts busy, those
> > mount points (with the busy mounts) don't get restarted. Autofs on
> > Solaris,however, will pick up those busy mounts and manage them
> > accordingly. Is this just the nature of autofs 3.1.3? Will version 4
> > work around this problem?
>
> Not really. You simply can't kill the daemon cleanly if its managing a
> busy mount-point. When automount gets a SIGTERM it will try its hardest
> to clean up and exit, but if either the autofs filesystem or one of the
> other mounted filesystems is busy, there's nothing it can do.
>
> The best that could possibly be done is to make it remember the pending
> termination request and have it exit when it finally (if ever) becomes
> idle.
>
At some point it was suggested to have SIGTERM take on the current
function of SIGUSR2, requiring SIGINT or something similar to force a
quit if the mount point is busy.
Currently:
SIGUSR1 - Expire but don't quit
SIGUSR2 - Quit if you can, but not if busy
SIGTERM - Quit unconditionally (but clean up)
SIGINT - Same
SIGKILL - Die, die, die (leaves a mess)
Proposed:
SIGUSR1 - Expire but don't quit
SIGUSR2 - Quit if you can, but not if busy
SIGTERM - Same
SIGINT - Quit unconditionally (but clean up)
SIGKILL - Die, die, die (leaves a mess)
The only problem with this is that the shutdown scripts tend to do
SIGTERM followed by SIGKILL, which would cause automount to get
SIGKILLed. On the other hand, at shutdown time it usually doesn't
matter.
-hpa
--
<[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
