On Mon, Jun 10, 2002 at 01:17:02PM -0400, James wrote:
I use: netstat -vat | grep LISTEN
That will tell you everything that is really listening on your server.
Not really, IIRC it will not show you udp servers.
You might want to check Tiger's test: check_listeningprocs
On Tue, 2002-06-11 at 11:39, Javier Fernández-Sanguino Peña wrote:
On Mon, Jun 10, 2002 at 01:17:02PM -0400, James wrote:
I use: netstat -vat | grep LISTEN
That will tell you everything that is really listening on your server.
Not really, IIRC it will not show you udp servers.
On Tue, Jun 11, 2002 at 11:57:34AM +0200, Bart-Jan Vrielink wrote:
As a native dutch speaker I find it very easy to remember 'netstat
-tulpen':
-t: tcp
-u: udp
-l: show only listening sockets
-p: show pid and program using the socket
-e: display aditional information.
-n: numeric output
Ryan J Goss wrote:
When I do a netstat -an, how do I properly decipher the output? To me it
looks like a lot of ports are listening, is there a way to determine what
daemon is running on those ports?
netstat -anp will tell you which processes.
lsof -i :port will tell you more specifically who
10, 2002 1:04 PM
To: Debian security mailing list
Subject: netstat output
When I do a netstat -an, how do I properly decipher the
output? To me it looks like a lot of ports are listening, is
there a way to determine what daemon is running on those ports?
--Ryan Goss [EMAIL PROTECTED
Do netstat -anp as root instead, it gives process pid and name
-Original Message-
From: Ryan J Goss [EMAIL PROTECTED]
Date: Mon, 10 Jun 2002 12:04:03 -0500 (CDT)
Subject: netstat output
When I do a netstat -an, how do I properly decipher the output? To
me it
looks like a lot of ports
6 matches
Mail list logo
