Date: Tue, 10 Apr 2007 10:00:02 +0200 From: Jonathan McKeown <jonathan@hst.org.za> To: freebsd-questions@freebsd.org Subject: Re: command to inentify the process that is listening in a port. Message-ID: <200704101000.03164.jonathan@hst.org.za> In-Reply-To: <461A5D9E.2010501@aeternal.net> References: <b713df2c0704090758h59657b8csc7716d3fe1f91943@mail.gmail.com> <b713df2c0704090759t1abcc96bld4978bbedec38687@mail.gmail.com> <461A5D9E.2010501@aeternal.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 09 April 2007 17:37, Martin Hudec wrote: > Siju George wrote: > > How Do you actually Identify what process is listening on a TCP/IP port? > > "nmap" does not usually give the right answer. > > There should be some command that can be run on the local host for > > identification right? > > man lsof > > 5:35pm [amber] ~# lsof -i @localhost:123 > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME > ntpd 552 root 10u IPv4 0xc4c46000 0t0 UDP localhost:ntp Just out of interest, why do so many people recommend lsof, which is a port, when sockstat/fstat are in the base system and seem to cover the same ground? Am I missing something about lsof? Jonathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200704101000.03164.jonathan>