FAIL_errno -> WARN_errno in V. 2.0
Dear Iperf Developers,
It appears that in Iperf V. 2.0 at some critical places such as the "socket()",
"bind()" and "accept()" system calls the "WARN_errno()" macro has been used
while in Iperf V. 1.6 and V. 1.7 at those places the "FAIL_errno()" macro had
been used. The result is that in Iperf V. 2.0 the program continues to run after
printing only a warning message.
What is the reason for this functionality?
Now it can happen that a server continues after a "bind()" to a port which is
already in use although it is never able to make a connection:
% iperf_20 -s -i 2
bind failed: Address already in use
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
The Iperf V. 1.X behaviour to exit with a non-zero exit status is in my point of
view more logical:
% iperf_17 -s -i 2
bind failed: Address already in use
% echo $status
1
%
Kind regards,
Hans Blom
NB: Excuses when you did receive this mail twice, but some time ago I changed
from email address and I got the impression that my previous mail did not
arrive at the list because I did not first update my iperf-users membership
which has yet been done.