SUMMARY: /net and remote mounting

From: Dave Wreski (dave@nic.com)
Date: Tue Feb 17 1998 - 06:47:46 CST


Hi all.

Thanks to:

Stephen Harris <sweh@mpn.com>
Ronald Loftin <reloftin@mailbox.syr.edu>
Casper Dik <casper@holland.Sun.COM>
Jeff Wasilko <jeffw@smoe.org>
Kevin Sheehan {Consulting Poster Child} <Kevin.Sheehan@uniq.com.au>
"DJEVANS.AU.ORACLE.COM" <DJEVANS@au.oracle.com>
Mariel Feder <mfeder@central.meralco.com.ph>
David Thorburn-Gundlach <david@bae.uga.edu>
Janet Hoo <Janet.Hoo@Ebay.Sun.COM>

My original question:

Hi all. To my amazement I ran GNU's updatedb from the root, and all of
the sudden I had a whole bunch of hosts mounted in /net, including my own
machine on /net/localhost.

I was pretty sure I deleted all packages relating to volume management.
How did this happen?

Answers: (I thought I had pkgrm'd automounter, so never even checked :( )

- This is the automounter, not the volume manager. Your
/etc/auto_master probably says something likd

        /net -hosts -nosuid

which says to use the hosts table/service to find the address and mount
the path from the server here under /net. The way this particular
mount works is to mount every exported filesystem on the remote machine
under /net/hostname, so that you can then go to the path you want (no,
you can't mount just one. bummer, eh?). It sounds like updatedb went
through your hosts file (is your host listed as /net/yourhost, too?)
and tried a mount from each one.

- If you want to avoid this, you have to comment the line regarding /net
on your /etc/auto_master file.

- Use the option "nobrowse" for that map.



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:31 CDT