From owner-freebsd-current Fri Jul 31 21:11:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26666 for freebsd-current-outgoing; Fri, 31 Jul 1998 21:11:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pobox.com (jaresh-5.mdm.mke.execpc.com [169.207.81.133]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA26659 for ; Fri, 31 Jul 1998 21:11:07 -0700 (PDT) (envelope-from hamilton@pobox.com) Message-Id: <199808010411.VAA26659@hub.freebsd.org> Received: (qmail 10118 invoked from network); 31 Jul 1998 23:14:06 -0500 Received: from localhost (HELO pobox.com) (127.0.0.1) by localhost with SMTP; 31 Jul 1998 23:14:06 -0500 To: lcremean@tidalwave.net Cc: current@FreeBSD.ORG Subject: Re: Identd problems on -current of 980724 In-reply-to: Your message of "Fri, 31 Jul 1998 23:15:53 EDT." <19980731231553.A545@st-lcremean.tidalwave.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 Jul 1998 23:14:06 -0500 From: Jon Hamilton Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG } > Did you recompile libkvm, reinstall it, and then recompile and install } > the identd? } } This was after a make world upgrade, so yes, libkvm should ahve updated. And } yes, I did recompile pidentd. You didn't explicitly say; did you also build a new kernel and reboot after that? } > You may also want to make sure it is running as root. If not, it will } > not be able to get a reserved port. } } It's running from inetd. As root? Inetd can start processes as any user, but if it worked before and you didn't change the configuration, it must have been set up to start as root. -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message