-------- Original Message --------
Subject: Re: sockets without processes
Resent-Date: Thu, 30 Aug 2001 19:36:51 -0700 (PDT)
Resent-From: debian-user@lists.debian.org
Date: Thu, 30 Aug 2001 19:28:27 -0700
From: Bob Galloway <[EMAIL PROTECTED]>
To: Martin F Krafft <[EMAIL PROTECTED]>,debian users
<debian-user@lists.debian.org>
References: <[EMAIL PROTECTED]>
On Fri, Aug 31, 2001 at 03:25:27AM +0200, Martin F Krafft wrote:
> tcp 0 0 192.168.14.6:32884 mailhost:smtp TIME_WAIT -
> tcp 0 0 192.168.14.6:32885 mailhost:smtp TIME_WAIT -
> tell me nothing about the process owning them.
> i am merely wondering why this is possible...
The clue is in the "TIME_WAIT" flag. The socket is in the late stage
of shutting down, probably because the process that opened that socket
is no longer running. If the process isn't running anymore, netstat
can't get at information about that process, since it doesn't keep
historical process data.
--
Bob Galloway "Vote Christia! I'm nice!"
-- Christia
Mulvey
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
tcp dumper 'n' portscanner with gravis joystick connectivity...go
configurwe...
