Re: Error when exiting server on Sun
Yes this is a long standing "problem" that has yet to have any progress
made. Since you are trying to stop the program at the time it is not
really seen as something that needs attention.
Kevin
PS: Sometimes there is also a segfault on exit and this also has not been
given much attention for reasons above.
On Wed, 12 Feb 2003, paul shields wrote:
> I also noticed the following error when I control-c the server on a Sun
> Solaris 8 machine. I assume there is just a small flow problem when catching
> the signal and shutting down.
>
> Paul
>
> ------------------------------------------------------------
> Server listening on UDP port 5001
> Binding to local address 192.168.3.200
> Receiving 1470 byte datagrams
> UDP buffer size: 8.00 KByte (default)
> ------------------------------------------------------------
> [ 3] local 192.168.3.200 port 5001 connected with 192.168.1.69 port 2034
> [ ID] Interval Transfer Bandwidth Jitter Lost/Total
> Datagrams
> [ 3] 0.0- 0.0 sec 1.44 KBytes 919 Kbits/sec 0.000 ms 0/ 1 (0%)
> [ 4] local 192.168.3.200 port 5001 connected with 192.168.1.69 port 2035
> [ ID] Interval Transfer Bandwidth Jitter Lost/Total
> Datagrams
> [ 4] 0.0- 0.0 sec 54.0 Bytes 8.00 Mbits/sec 0.001 ms 0/ 3 (0%)
> [ 3] local 192.168.3.200 port 5001 connected with 192.168.1.69 port 2036
> [ ID] Interval Transfer Bandwidth Jitter Lost/Total
> Datagrams
> [ 3] 0.0- 0.0 sec 72.0 Bytes 183 Kbits/sec 0.029 ms 0/ 4 (0%)
> [ 4] local 192.168.3.200 port 5001 connected with 192.168.1.69 port 2037
> [ ID] Interval Transfer Bandwidth Jitter Lost/Total
> Datagrams
> [ 4] 0.0- 0.0 sec 68.0 Bytes 128 Kbits/sec 0.028 ms 0/ 4 (0%)
> [ 3] local 192.168.3.200 port 5001 connected with 192.168.1.69 port 2038
> [ ID] Interval Transfer Bandwidth Jitter Lost/Total
> Datagrams
> [ 3] 0.0- 0.0 sec 54.0 Bytes 62.6 Kbits/sec 0.031 ms 0/ 3 (0%)
> ^Crecvfrom failed: Bad file number
>