Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!rice!sun-spots-request
From: rcc!pearlman@rand.org (Laura Pearlman)
Newsgroups: comp.sys.sun
Subject: Re: getwd() call problems
Keywords: SunOS
Message-ID: <3996@brazos.Rice.edu>
Date: 21 Dec 89 21:35:07 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 17
Approved: Sun-Spots@rice.edu
X-Refs:  Original: v8n221
X-Sun-Spots-Digest: Volume 8, Issue 228, message 8 of 18

In article <3880@brazos.Rice.edu> lamy@ai.utoronto.ca (Jean-Francois Lamy) writes:

> Using trace(1) you can easily determine that getwd() will not follow
> symbolic links.  So you can avoid this problem by making sure that all NFS
> entries in /etc/fstab are actually symbolic links (i.e. mount on  the
> symlink -- mount will follow the symlink at mount time and mount on the
> directory referenced by the symlink).

Perhaps I'm missing something obvious, but I don't see how this could
possibly help the situation at all.  If the /tmp/.getwd file is out of
date, the getwd function stats each mount point found in /etc/mtab; when
the mount program mounts a filesystem, it puts the real absolute pathname
of the mount point (not the name of the symlink found in /etc/fstab) into
/etc/mtab.

		-- Laura Pearlman
		   pearlman@rand.org