Socket Problem

Hi, I am running as root the command "netstat -alpn", I have a server
application running on RedHat3 kernel 2.4.21-37.
Sometimes netstat does not display the PID/Program name for several
connections ESTABLISHED to the server port, it just displays "-"
instead of the PID. Is this normal or expected behaviour of netstat? I
could not find anything about it with "man netstat". Any help will be
very appreciated.

Regards,
Seba
.

Relevant Pages

  • Re: SubSeven alerts: Norton Firewall vs Hacks/Trojan cleaner
    ... Personal Web Server -- PWS), mail servers, news servers, ftp servers, IRC ... | - use netstat with appropriate options to check for listening services ... firewall which make decisions as to what to ... As for the Subseven Alerts, again, Wolfgang is largely correct; ...
    (comp.security.firewalls)
  • Re: Wnidows Server 2003 - I need help in getting the Connection Co
    ... command if already running. ... it fires off the netstat command for you, sending the results from that to ... SHELL EXEC FUNCTION ON SERVER 2003 - PERMISION PROBLEM!!!!! ... requires administator access we are get file permison problems - ANY ...
    (microsoft.public.windowsmedia.server)
  • Re: Slow Box
    ... server, any scripts on the web site? ... Shared Hosting, Reseller Hosting, Dedicated & Semi-Dedicated servers ... For lsof and netstat, there are too many lines to paste. ...
    (comp.os.linux.misc)
  • Re: SQL Server does not exist or access denied.
    ... netstat -noa shows a bunch of local local processes, ... Dumb question first: The server is running? ... Look for the process ID of the server process in task manager. ... not being able to connect with port 1443. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Wnidows Server 2003 - I need help in getting the Connection Co
    ... exteral application in since it needs to run on Windows Server 2003. ... command if already running. ... it fires off the netstat command for you, sending the results from that to ... SHELL EXEC FUNCTION ON SERVER 2003 - PERMISION PROBLEM!!!!! ...
    (microsoft.public.windowsmedia.server)