nohide This option is based on the option of the same name provided in IRIX NFS. Normally, if a server exports
two filesystems one of which is mounted on the other, then the client will have to mount both filesys-
tems explicitly to get access to them. If it just mounts the parent, it will see an empty directory at
the place where the other filesystem is mounted. That filesystem is "hidden".
Setting the nohide option on a filesystem causes it not to be hidden, and an appropriately authorised
client will be able to move from the parent to that filesystem without noticing the change.
hello all,
I have a problem that just seem to show up. I was using autofs to mount home directory. It was working for about two week and now is just tsop working. I rebooted the erver and still not working. I can manually mount the directory but unable to mount via autofs. From the client I... (0 Replies)
Hi Guys,
Autofs works fine on AIX 5.2, but the same thing is not getting mounted automatically on AIX 5.3..
Is there ant difference for autofs confiiguration between 5.2 and 5.3
Thanks & Regards
Manu (0 Replies)
Hi Friends,
I am trying to configure autofs on rhel5.3 64bit to automount the nfs shares. It was working fine when i configured it first. After some days i can see its not working.
i can see the below sepcified error on the log file.
automount: rmdir_path: lstat of /NFS/test failed... (2 Replies)
I am trying to automount one of my NFS share to my client machine but it is not mounting
here is the scenario :
My server machine ip : 192.168.1.100
My client machine ip is : 192.168.1.102
on client machine i have configured the /etc/auto.master file :
/share(My mount point) ... (0 Replies)
I am running CentOS 6.3 as a VM on a host which has the same installation. I configured my NFS server and I am guessing it works. I say guessing because I can mount the desired folder with mount command on my client machine. So, when I run:
mount -t nfs -o vers=3 vm2.domain.com:/nethome /nethit... (7 Replies)
This is unfortunately for a Tru64 5.1 PK4 system.
I have Autofs running and it seems to read and mount the NIS maps, however, on a couple of maps, eventhough is says (rw), the user home directory of /home is (ro). See cut and paste Below. This prevents the automounting of Users home... (4 Replies)
Hi all,
Please help! After my solaris 10 is rebooted, I found my autofs seems not mounting the file systems.
I restart autofs service :
#svcadm -v restart svc:/system/filesystem/autofs:default
Action restart set for svc:/system/filesystem/autofs:default.
But still... (1 Reply)
Hi all,
I'm having trouble getting autofs working on a new install of Scientific Linux 7.2.
I have the files /etc/auto.master, /etc/auto/homes and /etc/auto.misc and /auto.direct setup, and they are copies of files on a working SL 6 machine. I can include the contents of the files at the end... (0 Replies)
Discussion started by: HuntWilliamR
0 Replies
LEARN ABOUT REDHAT
automount
AUTOMOUNT(8) System Manager's Manual AUTOMOUNT(8)NAME
automount - configure mount points for autofs
SYNOPSIS
automount [options] mount-point map-type[,format] map [map-options]
DESCRIPTION
The automount program is used to configure a mount point for autofs, the inlined Linux automounter. automount works by taking a base
mount-point and map file, and using these (combined with other options) to automatically mount filesystems within the base mount-point when
they are accessed in any way. The filesystems are then autounmounted after a period of inactivity.
OPTIONS -p, --pid-file
Write the pid of the daemon to the specified file.
-t, --timeout
Set the minimum timeout, in seconds, until directories are unmounted. The default is 5 minutes. Setting the timeout to zero dis-
ables unmounts completely.
-v, --version
Display the version number, then exit.
ARGUMENTS
automount takes at least three arguments. Mandatory arguments include mount-point, map-type and map. Both mandatory and optional argu-
ments are described below.
mount-point
Base location for autofs-mounted filesystems to be attached. This is a directory name which must already exist.
map-type
Type of map used for this invocation of automount. The following are valid map types:
file The map is a regular text file.
program
The map is an executable program, which is passed a key on the command line and returns an entry on stdout if successful.
yp The map is a NIS (YP) database.
nisplus
The map is a NIS+ database.
hesiod The map is a hesiod database whose filsys entries are used for maps.
ldap map names are of the form [servername:]basedn, where the optional servername is the name of the LDAP server to query, and
basedn is the DN to do a subtree search under. Entries are automount objects in the specified subtree, where the cn
attribute is the key (the wildcard key is "/"), and the automounterInformation attribute contains the information used by the
automounter. Documentation on the schema used by this module is available online at http://docs.iplanet.com/docs/manu-
als/directory/411ext/nis/mapping.htm.
format Format of the map data; currently the only formats
recognized are sun, which is a subset of the Sun automounter map format, and hesiod, for hesiod filesys entries. If the format is
left unspecified, it defaults to sun for all map types except hesiod.
map Location of mapfile to use. This is an absolute UNIX pathname in the case for maps of types file or program, and the name of a
database in the case for maps of type yp, nisplus, or hesiod.
options
Any remaining command line arguments without leading dashes (-) are taken as options (-o) to mount. Arguments with leading dashes
are considered options for the maps.
NOTES
If the automount daemon catches signal USR1, it will unmount all currently unused autofs-mounted filesystems and continue running (forced
unmount.) If it catches signal USR2 it will unmount all unused autofs-mounted filesystems and exit if all filesystems were unmounted.
Busy filesystems will not be unmounted.
SEE ALSO autofs(5), mount(8).
BUGS
A whole slew of missing desirable features (see TODO file).
The documentation leaves a lot to be desired.
Please report other bugs along with a detailed description to <autofs@linux.kernel.org>. To join this mailing list, send a message with
the line "subscribe autofs" to <majordomo@linux.kernel.org>.
AUTHOR
H. Peter Anvin <hpa@transmeta.com>
19 Jun 2000 AUTOMOUNT(8)