On Jun 17, 2010, at 12:48 PM, Edward Ned Harvey wrote: > Yessss.... > > man nfslogd > (and google nfslogd, etc) > totally nailed it. Thank you Cameron.
Before you get too happy... NFS logging can have a severe negative impact on performance and scaling. Not recommended for anyone with lots of active clients. Meanwhile, you might look into some of the dtrace scripts available now because of the new NFS provider. http://wikis.sun.com/display/DTrace/nfsv3+Provider -- richard > Just incase anyone stumbles across this by search, here's the start-to-end > answer: > man nfslogd > First, edit /etc/default/nfslogd I am using: > MIN_PROCESSING_SIZE=1 > IDLE_TIME=1 > Assuming you already have svc:/network/nfs/server:default enabled > If you are using /etc/dfs/dfstab instead of the sharenfs property, just add > ",log" as specified by man share_nfs > If you wish, run that share command now. > By simply adding ,log to the dfstab, nfslogd will automatically start > after reboot > or start it manually now: /usr/lib/nfs/nfslogd > If you are using the sharenfs property instead of dfstab, just figure out how > to add the ,log option > tail -f /var/nfs/nfslog > > Again man nfslogd. Information in the log won't be complete until NFS > services are restarted, which is well documented in the man page. > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss -- Richard Elling rich...@nexenta.com +1-760-896-4422 ZFS and NexentaStor training, Rotterdam, July 13-15, 2010 http://nexenta-rotterdam.eventbrite.com/ _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
