Date: Fri, 21 Sep 2007 22:17:56 +0200 From: Albert Shih <Albert.Shih@obspm.fr> To: Dan Nelson <dnelson@allantgroup.com> Cc: Le Cocq Michel <Michel.Lecocq@lipn.univ-paris13.fr>, freebsd-questions@freebsd.org Subject: Re: How to know who use NFS. Message-ID: <20070921201756.GB85057@pcjas.obspm.fr> In-Reply-To: <20070921185934.GI7562@dan.emsphone.com> References: <20070920172428.GA90565@pcjas.obspm.fr> <46F3F2C8.20806@lipn.univ-paris13.fr> <20070921185934.GI7562@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Le 21/09/2007 à 13:59:35-0500, Dan Nelson a écrit > In the last episode (Sep 21), Le Cocq Michel said: > > Albert Shih a écrit : > > > Sometime I've a user (or some users but not lot of users) make a > > > very huge transfert through NFS. I don't want that. > > > > > > How can I known at un precise moment who charge my NFS server (I'm > > > root in both side : client and server). > > > > With some info student it also happen some times in here, and the way i > > find is to launch a tcpdum or ethereal on the server and look at which > > ip appear the more often > > I think ethereal/wireshark is your best bet too. At least with it you > can filter on the userid making an NFS request (it's rpc.auth.uid). > Unfortunately it doesn't look like there's a summary or analysis option > for NFS, so you'll have to count packets maually... Thanks for that. But my problem is the NFS traffic is heavy in standard time, and wireshark or tcpdump give my lot of lot of data. But I'm going to try again. Regards. -- Albert SHIH Observatoire de Paris Meudon SIO batiment 15 Heure local/Local time: Ven 21 sep 2007 22:16:34 CEST
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070921201756.GB85057>