Hi Tru64 colleagues.
I am debugging a component based WEB application on Tru64 5.0 and I believe
I have found a bug in the Tru64 TCP stack.
Basically it boils down to the following:
- open a socket to the server
- write some bytes
- read some bytes
- call the shutdown(fd,2) system call on this socket
- close the socket.
Here is some output from the application's debug log file...
ident - UNIX system:OSF1 node:163.228.104.20 release:V5.0 version:1094
machine:alpha
12:21:50 - opsys - socket open(): fd=9
12:21:50 - opsys - socket connect(fd=9,address='163.228.104.20:1705')=0
12:21:50 - distr - W="t"
12:21:50 - distr - R="T162:962626658"
12:21:50 - opsys - socket close(fd=9)=-1: errno=22: Invalid argument
12:21:50 - opsys - socket close(fd=8)=0
When this is done, the close() system call fails with the "Invalid
argument" error.
AFAIK, this is not a documented error for the close system call.
Furthermore, the socket does get closed. From what I can tell, this is
clearly an OS bug. (The same application runs without errors on a Tru64
4.0F box).
Has anyone seen this behavior before on Tru64 5.0? Is there a patch to
correct the problem?
Thanks!
Regards,
Jim
--------------------------------------------------------
FSC - Building Better Information Technology Solutions-
from the Production Floor to the Customer's Door.
--------------------------------------------------------
Jim Jennis, Technical Director for Commercial Systems
Fuentez Systems Concepts, Inc.
1 Discovery Place, Suite 2
Martinsburg, WV. 25401
USA
Phone: +001 (304) 263-0163 ext. 235
Fax: +001 (304) 263-0702
Email: jjennis_at_discovery.fuentez.com
jhjennis_at_shentel.net
WEB:
http://www.discovery.fuentez.com/
Received on Wed Jul 05 2000 - 14:08:53 NZST