:~>Has anyone else killed 'amd' permanently and lived to tell the tale !!
I have been using both "amd" and "autofs" since the "autofs" came to life,
and i can assure you that "autofs" runs much more reliably than amd.
Therefore, I use autofs to mount "homes" (every machine exports its home
directory to "thrusted-hosts" netgroup, and autofs mounts all the "home"
directories it can see to /homes/MACHINE). Basically, these "homes"
directories have never given me any headache.
Then, I had to add an user whose home-directory came from completely
different system, and it was not exported as "home", but as
"home/MACHINE", or so - and I thought - what the hell, I will just give
him a "/net/MACHINE/home/MACHINE" path to his home-directory and forget
about it. Guess what? Several days later, amd got stuck and a few days of
calculations were gone. This happened repeatedly, so i had to add a rule
to "autofs" config file and everything works OK since then.
I still keep "amd" running with default settings, because i cannot bring
the "autofs" to mount "anything" under "/net" the way amd does (anybody
knows how to do it), but I do not use it for anything crytical anymore.
:~>The auto-mount of amd is not necessary but I take it that means I would
:~>have to manually 'mount' each file system/partition ? My brain is tired
:~>again so bear with me
:~>if this is all common knowledge...???
Either that, or you mount everything from "fstab" or you let the "autofs"
do it.
cu
Denis
-----------------------------------------------------
Mag. Denis Havlik <http://www.ap.univie.ac.at/users/havlik>
University of Vienna ||| e-mail: [EMAIL PROTECTED]
Austria (@ @) tel: (++431) 4277/51179
-------------------oOO--(_)--OOo---------------------
