04-01-2005 09:16 AM
Version: Tru64 Unix V5.1A with PK6
Solved! Go to Solution.
04-03-2005 08:09 PM
04-03-2005 08:18 PM
04-04-2005 04:36 AM
Build and install the tool, and run the command with the options:
lsof -i :xxxx
where xxxx is the port your program is using, and it will show any programs holding the port open. If you were using a debugger to look at the program, it may have held the port open after you were done looking at the program and did not exit from the debugger program.
Best wishes for solving the problem,
04-04-2005 06:55 PM
We had similar issue with envmond daemon, which can't start at boot time because its ports were used temporary by another process for outgoing connection.
To avoid listening/outgoing collision ports, we used 2 inet_sys parameters :
By default, Tru64 use port beginning at 1024 for outgoing connection.
09-16-2005 05:13 AM
netstat -na | grep
- I'd guess the port shows being in state FIN_WAIT_2.
I haven't yet found documentation on how this timeout is influenced on Tru64 [sysctl, ndd, whatever] and don't have access to my test system in the next time, so You might want to ask HP :)
(As a reference On HP-UX is goes by the name of 'tcp_fin_wait_2_timeout')
09-16-2005 05:15 AM
09-21-2005 12:15 AM