FC2 automounter differences (hesitant to call them bugs.)
Dan
ml at mutox.org
Thu May 20 01:55:43 UTC 2004
I also noticed the changes and i checking out the autofs docs.
With regards to your problem 1, I think its a known issue.
Check out /usr/share/doc/autofs-4.1.2/README.direct
<snip>
NOTE: Due to current design limitations, direct maps will take over an
entire directory hierarchy. What this means is, if your direct map
key is /usr/share/bilbo, then /usr will become an automount mount
point, mounting over the existing /usr.
</snip>
On Thu, 2004-05-20 at 10:31, Greg.Lehmann at csiro.au
> Scenario is a solaris yp master that serves up yp maps.
>
> PROBLEM 1.
> I have direct mounts specified in the auto_master file on solaris as
> specified by the first line below. Direct mounts are a sun specific
> add-on, and while I am moving away from them, FC1 did not cause me any
> trouble. FC2 is trying to do something with them. I think all of my
> direct mounts are under /usr and what is now happening is that FC2
> automounter is taking over /usr as a mount point and there is basically
> an empty /usr because of this. This causes a bit of havoc. Removing the
> first line fixes the problem.
>
> Auto_master
> #Mount-point Map Mount-options
> /- auto_direct -rw,intr
> /home auto_home -rw,intr,nobrowse
> /data auto_data -rw,intr,nobrowse
> /apps auto_apps -rw,intr
> /net -hosts
>
> Example line from auto_direct.
>
> /usr/corel server:/export/site/apps/corel
>
> PROBLEM 2.
> The nobrowse option causes all the mounts under /data and /apps (as
> shown above) to fail. Removing the nobrowse option allows them to work.
>
> Is this the way automount is supposed to work or is it a bug(s) I need
> to file?
>
More information about the fedora-test-list
mailing list