From owner-freebsd-net@freebsd.org Thu Nov 5 07:46:38 2015 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1EB88A26E0C for ; Thu, 5 Nov 2015 07:46:38 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 67CFB13D7 for ; Thu, 5 Nov 2015 07:46:36 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id JAA29972; Thu, 05 Nov 2015 09:46:34 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1ZuFFi-0005rO-1o; Thu, 05 Nov 2015 09:46:34 +0200 Subject: Re: who uses this port? To: Ben Woods , "freebsd-net@freebsd.org" References: <563A5F39.7010906@FreeBSD.org> From: Andriy Gapon Message-ID: <563B0922.9030805@FreeBSD.org> Date: Thu, 5 Nov 2015 09:45:38 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2015 07:46:38 -0000 On 05/11/2015 09:20, Ben Woods wrote: > On Wednesday, 4 November 2015, Andriy Gapon > wrote: > > $ sockstat -l | fgrep 631 > ? ? ? ? tcp4 127.0.0.1:631 > *:* > > $ nc -l 127.0.0.1 631 > nc: Address already in use > > > > I'm more curious as to why sockstat gives you question marks instead of the > proper process details. Any ideas? Yeah, I should have stated my question more accurately. What you are asking is what I actually intended to ask. I was debugging a problem of cupsd not being able to bind to its port after a restart. Eventually I had to reboot the affected system. -- Andriy Gapon