ndt-users list created

[Clayton Keller <>]

 wrote:
> This is running on a P4...but it's not 64bit arch.
>
> One thing I did see different when looking at debug on the working platform ( 
> Fedora Core 2 on a P3) is this:
>
> # ./web100srv -ddd -m -l /var/log/web100/web
>  Reading config file /etc/ndt.conf to obtain options
> ANL/Internet2 NDT ver 3.1.4
>         Variables file = /usr/local/ndt/web100_variables
>         log file = /var/log/web100/web
>         Debug level set to 3
> server ready on port 3001
> web100_init() read 69 variables from file
> Initial counter Values Totalcnt = 0, Total Mismatch = 0, Total Bad Cables = 0
> Updated counter values Totalcnt = 1, Total Mismatch = 0, Total Bad Cables = 0
> Individual counts = [0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0]
> Initial counter Values Totalcnt = 1, Total Mismatch = 0, Total Bad Cables = 0
> Updated counter values Totalcnt = 2, Total Mismatch = 0, Total Bad Cables = 0
> Individual counts = [0,0,0,0,0,0,2,0,0,0,0,0,0,0,0,0]
> Signal 17 received from process 11145
> successfully locked '/tmp/view.string' for updating
> sending '85849,80213,92479,92455,2,0,0,0,0,0,0,0,0,2,0,0,0,0,0,0,0,0,0,Aug 30 
> 11:23:08,Aug 30 11:23:08' to tmp file
> nothing in queue
> Timer not running, waiting for new connection
>
> However, when running on the newer system, I do not see much of this on the 
> newer P4 setup:
>
> # /usr/local/sbin/web100srv -ddd -m -l /var/log/web100/web100srv.log
>  Reading config file /etc/ndt.conf to obtain options
> ANL/Internet2 NDT ver 3.1.4
>         Variables file = /usr/local/ndt/web100_variables
>         log file = /var/log/web100/web100srv.log
>         Debug level set to 3
> server ready on port 3001
> web100_init() read 69 variables from file
> Signal 17 received from process 17281
> successfully locked '/tmp/view.string' for updating
> sending '0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,,' to tmp file
> nothing in queue
> Timer not running, waiting for new connection
>
> What generates the information that is set to the tmp file? And any ideas why 
> it is not sending similar information? Is this something your patches are 
> designed to help with?

After patching the source, I am still seeing the same issue as before. 
Any further assistance and suggestions is much appreciated.