Subject: Re: bin/36506: /etc/rc.d/amd prohibits reboot if amd owns /home
To: None <gnats-admin@netbsd.org, netbsd-bugs@netbsd.org,>
From: Matthias Scheler <tron@zhadum.org.uk>
List: netbsd-bugs
Date: 06/18/2007 12:05:04
The following reply was made to PR bin/36506; it has been noted by GNATS.

From: Matthias Scheler <tron@zhadum.org.uk>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: bin/36506: /etc/rc.d/amd prohibits reboot if amd owns /home
Date: Mon, 18 Jun 2007 13:00:38 +0100

 On Sun, Jun 17, 2007 at 07:00:01PM +0000, Hauke Fath wrote:
 >  What sounds like a good idea ends up blocking a reboot if
 > (1) amd manages nfs mounts under /home, and
 > (2) a shutdown -r is issued by a non-root member of group operator
 > with a home directory managed by amd..
 
 Why should that block the reboot? All the process should use
 "/amd/server/what/ever/serverfilesystem" and not "/home" anyway.
 
 > >Fix:
 > 
 > Implement a timeout for the unmount attempt (10..15 sec should be
 > acceptable), make gracefully shutting down amd an option (default
 > off), or just back out the change. Note that this change has trickled
 > down to one or more release branches.
 
 Backing out that change is not an option. I've added it because
 I frequently had problems with unmounting filesystem on my server
 during a shutdown or reboot.
 
 This happened because the amd(8) process got terminated but the
 pseudo NFS mounts were still active. The kernel tried to unmount
 them but didn't succeed because the NFS request didn't get handled.
 
 	Kind regards
 
 -- 
 Matthias Scheler                                  http://zhadum.org.uk/