From: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>
Subject: Re: File monitoring
Date: Sun, 28 Jan 2007 17:49:11 -0500
Message-ID: <20070128224911.GA18039@ti64.telemetry-investments.com>
References: <Pine.LNX.4.61.0701272123470.22295@yvahk01.tjqt.qr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: nfs@lists.sourceforge.net
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
In-Reply-To: <Pine.LNX.4.61.0701272123470.22295@yvahk01.tjqt.qr>
Sender: nfs-bounces@lists.sourceforge.net
Errors-To: nfs-bounces@lists.sourceforge.net

On Sat, Jan 27, 2007 at 09:31:42PM +0100, Jan Engelhardt wrote:
> as part of implementing a netboot solution, I observe that the client 
> pulls about 128 MB of data (measured in iptraf, so it includes 
> IPv4 headers too). You probably agree that this contributes to a boot 
> that could possibly be sped up (even if the same distribution was to 
> read from local disk). I wonder what files it actually accesses. Is 
> there some utility to get a listing of all the files that were accessed? 
> tcpdump provides a nice hint, e.g.
 
For testing, try using UNFS3 ( http://unfs3.sourceforge.net ), a userspace
NFSv3 server implementation, rather than the in-kernel knfsd server.  It should
be a simple matter to hack up the server code to log the client file accesses.

Regards,

	Bill Rugolsky

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs