19 Jul
2002
19 Jul
'02
16:45
Anders
So what happened was that the process that bound the port had time to die in between the "fuser" and the "grep". Try
fuser -v port/tcp
to get a little more verbose output, including the name of the command. You may want to run the netstat again, in case the port numbers have changed.
Ports are the same... result of 'fuser -v 1403/tcp' USER PID ACCESS COMMAND 1403/tcp root 30504 f.... squid the f... bit is as it is on the screen in front of me. Thanks -- Richard