Control: forwarded -1 http://sourceforge.net/p/nfswatch/bugs/1/ Control: tags -1 + confirmed upstream help
Hi Petter, On Wed, Oct 15, 2014 at 12:10:41PM +0200, Petter Reinholdtsen wrote: > Package: nfswatch > Version: 4.99.11-3 > Severity: important > > Hi. I tried to use nfswatch to get an overview of the NFS traffic, > but the screen is filled with messages looking simliar to this: > > > nfs3_count: length is 00000024, proc s 1 > 01000701 > 02f00700 > 00000000 > nfs3_count: > length is ... > > and so on and so forth. This is scrolling over the screen so quickly > that it is almost impossible to read the text. > > Is this some runaway debug message that could be supressed? > > Btw, running nfswatch under valgrind note that a call to the bind() > system call is used with uninitialized bytes. Perhaps something to > look at? > > Setting severity to important, as this make the program almost useless. I know about this problem, and it is also reported upstream at [1]. Upstream has long time not haved activity unfortunately. Any help with this issue would be really appreciated (in case you have some free time to look into it and check for a possible patch). [1] http://sourceforge.net/p/nfswatch/bugs/1/ Regards, Salvatore p.s.: nfswatch for example also does not support NFSv4, so if you know some good alternative to nfswatch please let me know. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
