From owner-freebsd-questions Thu Jul 15 13:43: 0 1999 Delivered-To: freebsd-questions@freebsd.org Received: from drama.navinet.net (drama.navinet.net [216.67.14.8]) by hub.freebsd.org (Postfix) with ESMTP id 2CB841561C for ; Thu, 15 Jul 1999 13:42:32 -0700 (PDT) (envelope-from forrie@forrie.net) Received: from forrie.net (forrie.net [216.67.12.69]) by drama.navinet.net (8.9.3/8.9.3) with ESMTP id QAA05047 for ; Thu, 15 Jul 1999 16:40:56 -0400 (EDT) Received: (from forrie@localhost) by forrie.net (8.9.3/8.9.3) id QAA64423 for freebsd-questions@freebsd.org; Thu, 15 Jul 1999 16:40:51 -0400 (EDT) Date: Thu, 15 Jul 1999 16:40:51 -0400 From: Forrest Aldrich To: freebsd-questions@freebsd.org Subject: Many identd instances Message-ID: <19990715164051.A64416@forrie.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There's something very wrong with how identd has been acting (on my machine, anyways). This is FreeBSD-3.2-STABLE (and updated). Despite the switches to timeout, often times I'll log in and find tens of identd daemons running-- and I have to killall them. If I limit the instances through xinetd, then lots of things that require ident reponses don't work. I've recompiled identd several times, and it still seems to happen. This does not happen on my 2.2.8-based systems. It is the pidentd port. Anyone see this behavior? -F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message