Automounter uses a configuration file and some additional application support to allow a client system to mount a specific remote file system on demand. Yast is aware of it (check the NFS client dialog), or add the automounter package via 'rpm -i' and check out the man page.
The high level version is that you load the automounter package, establish a set of local mount points for the various file systems, and set up the automounter map file to indicate which remote file systems should be mounted on which local mount points when a user cd's into the local mnt point directories (along with some miscellaneous timeout information, etc). Then you just turn it on and let it go. Automounter gets invoked when an application references something on the local mount point. When no users have accessed a file on the automounted file system for a specified period, it's automagically unmounted. It's useful, but read docs carefully. Some of the behavior can be a little tricky to understand. -- db > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > Behalf Of James Melin > Sent: Wednesday, November 23, 2005 11:24 AM > To: [email protected] > Subject: Re: Dynamically making NFS shares available/unavailable > > Very interesting twist David, as always. Can you point me in > a direction to research automounter? Never heard of if > before. I know about IP restricting the shares. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
