[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: bin/38103: automounter (amd) failed to unmount busy filesystems on reboot - reboot will hang
On Feb 27, 1:20pm, tron%zhadum.org.uk@localhost (Matthias Scheler) wrote:
-- Subject: Re: bin/38103: automounter (amd) failed to unmount busy filesyste
| The following reply was made to PR bin/38103; it has been noted by GNATS.
| From: Matthias Scheler <tron%zhadum.org.uk@localhost>
| To: NetBSD GNATS <gnats-bugs%NetBSD.org@localhost>
| Subject: Re: bin/38103: automounter (amd) failed to unmount busy filesystems
on reboot - reboot will hang
| Date: Wed, 27 Feb 2008 13:18:09 +0000
| On Tue, Feb 26, 2008 at 10:10:17AM +0100, Wolfgang Stukenbrock wrote:
| > Hi, here ist our amd configuration, but I don't think this is the cause
| > of the problem.
| > /etc/amd.conf:
| > [ global ]
| > map_type = nis
| > browsable_dirs = no
| > normalize_hostnames = yes
| > fully_qualified_hosts = yes
| > unmount_on_exit = yes
| > restart_mounts = yes
| > local_domain = nagler-company.com
| I disagree. I think the "unmount_on_exit" causes the problem. I'm not
| using that option and it works for me.
| Anyway, I've backed out the change to "/etc/rc.d/amd" already.
| amd(8) is a lost cause and should be removed from NetBSD as
| soon as possible.
Great attitude here, "hands hurts: cut it off". I am using amd on ~500
machines here and it works just fine. What's the alternative, don't cross
mount between machines? Perhaps the problem is that amd stops too late,
and nfs or the network is not running anymore?
Main Index |
Thread Index |