Thus spoke H. Peter Anvin on 22-Feb-99 :
>>
>>
>> I imagine the official line on this is that you don't need to restart
>> an automount process because you can just change the map file and it
>> should take effect immediately. The "autofs reload|restart" only kills
>> or starts mounts which have changed in the auto.master file.
>>
>> I guess I'll either have to kill those processes or permanently mount
>> the directories until the next reboot!
>>
>
> Basically, in autofs v3 there is no way of taking control over an
> abandoned automount, and I haven't been planning on that kind of
> support for autofs v4 either; it is really hard to do and I see very
> little benefit to it.
I disagree that this feature has "little benefit". Imagine, you want to
move a user from one partition to another. That happens sometimes if you
are a sysadmin. Changing NIS maps will not solve the problem.
Yep, then you end up rebooting the machines or tell the user, he/she can only
log onto machines, which have been not used by him/her.
Or is there another simple official procedure, how to deal with these situations
and avoid reboot?
That is IMOP the major drawback of autofs versus good old AMD, we did use
before. AMD could be restarted with no problems. The only reason, we switch to
autofs was, that LINUX mount changed over the years and the AMD linux mount
code is not maintained any more.
Frithjof
"If you see someone without a smile, give him one of yours"
Frithjof Anders
Institut fuer Festkoerperphysik
Technische Universitaet Darmstadt
Hochschulstr. 6
64289 Darmstadt, GERMANY
Tel +49 (6151) 16-5235 email: [EMAIL PROTECTED]
FAX +49 (6151) 16-3681
