First, let me describe the problem. I use autofs at work on a RedHat 6.2 system to mount corporate nis maps for users in /home, for applications in /apps and for public stuff in /pub. I also use autofs to access various nfs servers, one floppy disk drive and 2 cdrom drives in /misc. This setup worked fine until I decide to use /mnt for the mount points previously located in /misc. The /etc/fstab file contains all these /mnt entries with the "noauto" option. These file systems should not be mounted at boot time or when the "mount -a" is invoked according to the mount and fstab manual pages. But, If I invoked "mount -a", the floppy disk drive, the cdroms and the nfs entries are scanned even if the "noauto" option is specified in the /etc/fstab file. The "mount -a" command takes long time to complete and if a floppy or a cdrom is inserted, these devices are mounted. The nfs servers are also mounted. Then, the mount command does not behave correctly.
If autofs is not running, the "mount -a" command does exactly what it is supposed to do and the command goes really faster. I am wondering if the mount command try to check the mount point presence before scanning the options provided in the /etc/fstab file ? This can cause the file systems to be mounted anyway because autofs mount them when they are accessed...
This mount/autofs behavior can also affect other programs. By example, if you right mouse click in the GNOME background environment, a scan of the devices in /etc/fstab file is performed with the mount command (I guess) and this feature takes long time to accomplish. The popup window comes to the screen at least 10 seconds after the mouse click !!!
Is there somebody using autofs that has already noticed this problem ? Is there a workaround ?
Thanks,
Claude.
-- Claude LeFrançois, System and Network Administrator Ericsson Research Canada (LMC) 8300 Décarie, Ville Mont-Royal, Québec, Canada, H4P 2P5 Tel: (514) 345-7900 x7579, Fax: (514) 345-6149 Email: [EMAIL PROTECTED]
