From owner-freebsd-questions Thu May 25 0:41: 3 2000 Delivered-To: freebsd-questions@freebsd.org Received: from web2.sea.nwserv.com (web2.sea.nwserv.com [216.145.16.2]) by hub.freebsd.org (Postfix) with ESMTP id 208C737BBF0 for ; Thu, 25 May 2000 00:41:00 -0700 (PDT) (envelope-from dpk@nwserv.com) Received: from localhost (dpk@localhost) by web2.sea.nwserv.com (8.9.3/8.9.2) with ESMTP id AAA97571; Thu, 25 May 2000 00:40:53 -0700 (PDT) (envelope-from dpk@nwserv.com) Date: Thu, 25 May 2000 00:40:53 -0700 (PDT) From: David Kirchner X-Sender: dpk@web2.sea.nwserv.com To: Oscar Ricardo Silva Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Port 722 ? In-Reply-To: <4.2.2.20000523190214.00a976c0@mail.utexas.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Envelope-To: oscars@mail.utexas.edu Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just looked at the new default config file, from today's cvsup. In the conf file there's a: #Port 722 # Secondary port to listen on It might not have been commented out in earlier versions of the port/tarball, not sure. The README explains why the option is available - basically it's an example of a new feature patched in to help you prioritize traffic with your router. -- David Kirchner - dpk@nwserv.com Northwest Web Services - http://www.nwserv.com/ On Tue, 23 May 2000, Oscar Ricardo Silva wrote: > Thanks to Dave Kirchner and Alan Clegg for the incredibly fast and > completely useful responses. Using both methods, I found out this: > > amanda# /usr/local/sbin/lsof -i TCP:722 > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME > sshd1 143 root 3u IPv6 0xcb8e7940 0t0 TCP *:722 > sshd1 143 root 5u IPv4 0xcb8e7720 0t0 TCP *:722 (LISTEN) > > Now the question is, where the hell did this come from? I hadn't seen this > before and I thought I'd checked my machine. > > > Oscar > > At 07:35 PM 5/23/00 -0400, Alan Clegg, you wrote: > >Out of the ether, David Kirchner spewed forth the following bitstream: > > > > > An easy way to find out what an unknown port is: > > > > > > First run 'netstat -aAn | grep LISTEN | grep \.portnum'. The -A flag will > > > display the address for the socket. You can then figure out which process > > > is using that address by running 'fstat | grep address': > > > > > > dpk@web2:/home/dpk$ netstat -aAn | grep LISTEN | grep \.25 > > > c6400180 tcp 0 0 *.25 *.* LISTEN > > > dpk@web2:/home/dpk$ fstat | grep c6400180 > > > root sendmail 94903 4* internet stream tcp c6400180 > > > >Easier way: > > > > lsof -i TCP:_portnum_ > > > >ecto 101} /usr/local/sbin/lsof -i TCP:25 > >COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME > >tcpserver 381 qmaild 3u IPv4 0xc735c500 0t0 TCP *:smtp (LISTEN) > > > >lsof from ports, btw... > > > >AlanC > >-- > > \ Alan B. Clegg > > Just because I can \ abc@firehouse.net > > does not mean I will. \ > > \ > > > > > "Don't believe the hype" > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message