Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: brent%terra@sun.com (Brent Callaghan)
Newsgroups: comp.sys.sun
Subject: Re: automounter peculiarity, and a nice automount example
Message-ID: <82829@sun.uucp>
Date: 3 Jan 89 22:56:01 GMT
References: <8812142340.AA00290@kahala.hig.Hawaii.Edu>
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 18
Approved: Sun-Spots@rice.edu
Original-Date: 22 Dec 88 18:06:12 GMT
X-Sun-Spots-Digest: Volume 7, Issue 86, message 1 of 12

Watch out for relative references between filesystems.  There may be an
implicit assumption that all three filesystems within /usr/local are
concurrently mounted - this may not be true using a map like the above
example.

For example: a symbolic link "/usr/local/bin/foo" could be a reference to
"../lib/foo".  The symbolic link will fail if "/usr/local/lib" isnt
currently mounted.  The automounter will not do the mount because the
relative pathname doesn't go through the automounter's mount point
(/usr/local).

BTW: It's not a good idea to mount executables "soft".  If the server goes
down while the executable is running you can get a SEGV or similar crash
when a page-in fails.  I prefer "hard,intr".

	Brent Callaghan  @ Sun Microsystems
	uucp: sun!bcallaghan
	phone: (415) 336 6188