Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: koreth@ssyx.ucsc.edu (Steven Grimm)
Newsgroups: comp.sys.sun
Subject: ftp logging
Message-ID: <8901202205.AA03893@ssyx.ucsc.edu>
Date: 28 Jan 89 07:35:36 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 15
Approved: Sun-Spots@rice.edu
Original-Date: Fri, 20 Jan 89 14:05:36 PST
X-Sun-Spots-Digest: Volume 7, Issue 126, message 8 of 12

>Looking at these patches, I can't see how they work for anonymous ftp
>(they appear to work for regular users).  The only way I can see these
>patches working with anonymous ftp is iff the anonymous ftp directory is
>/.  The reason I make this statement is because the log file is opened
>before the chroot.  After the chroot, you can no longer access the file.

Not true.  Once a file is open, it doesn't matter where it is on the
directory tree.  The filesystem already has a dev/inode pair for the file,
and it doesn't matter WHERE in the directory tree that pair is.  As
evidence, I offer the fact that my ftp logging patches work, and have been
working for quite a while now.

[[ The chroot-ed environment only matters when a file is opened.  Once you
have an open file descriptor, any amount of chroot-ing isn't going to
affect it.  --wnl ]]