From owner-freebsd-questions@FreeBSD.ORG Mon Apr 9 15:37:06 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DFAF016A406 for ; Mon, 9 Apr 2007 15:37:06 +0000 (UTC) (envelope-from corwin@aeternal.net) Received: from amber.aeternal.net (amber.aeternal.net [212.232.17.148]) by mx1.freebsd.org (Postfix) with ESMTP id 9E4B013C45D for ; Mon, 9 Apr 2007 15:37:06 +0000 (UTC) (envelope-from corwin@aeternal.net) Received: from localhost (localhost.aeternal.net [127.0.0.1]) by amber.aeternal.net (Postfix) with ESMTP id 29C38B821 for ; Mon, 9 Apr 2007 17:37:04 +0200 (CEST) X-Virus-Scanned: by amavisd-new at aeternal.net Received: from amber.aeternal.net ([127.0.0.1]) by localhost (amber.aeternal.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ba6dT5Vmn7Vz for ; Mon, 9 Apr 2007 17:37:03 +0200 (CEST) Received: from [155.208.254.69] (bbnrel6.net.external.hp.com [155.208.254.69]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: corwin@aeternal.net) by amber.aeternal.net (Postfix) with ESMTP id 859A2B81D for ; Mon, 9 Apr 2007 17:37:03 +0200 (CEST) Message-ID: <461A5D9E.2010501@aeternal.net> Date: Mon, 09 Apr 2007 17:37:02 +0200 From: Martin Hudec User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: command to inentify the process that is listening in a port. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: corwin@aeternal.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2007 15:37:07 -0000 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 Martin