On Mon, Mar 07, 2005 at 12:18:03PM -0800, David M. Fetter wrote:
David,
> Restarting AMD while it is in use is a serious problem.
restarting AMD is usually not a problem. You should use
the restart_mounts option or you have to clean up the
mounts yourself. You should not use the unmount_on_exit
option because unmounting might not work if a filesystem
is busy.
> Since amd has
> low level hooks into kernel space, if users or processes happen to be
> using an area that is automounted via AMD and it restarts on them, it
> basically can cause the entire server to come to a crashing halt.
Areas that are automounted are conventional mounts that are not
affected by AMD. AMD just provides links and, unlike autofs,
doesn't hook into kernel space.
More of a problem are NFS servers that do not respond. This may
freeze amd when it tries to unmount such a server and often causes
large delays when it tries to restart an existing mount to
such a server. If you automount /home or use an automounted
directory accessed in the shell profile you may not be able
to log into the server anymore.
If your entire server comes to a crashing halt then something else
is wrong.
Greetings,
--
Michael van Elst
Internet: [EMAIL PROTECTED]
"A potential Snark may lurk in every tree."
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List openpkg-dev@openpkg.org
