From owner-freebsd-questions Mon Feb 1 13:16:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17423 for freebsd-questions-outgoing; Mon, 1 Feb 1999 13:16:37 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17415 for ; Mon, 1 Feb 1999 13:16:34 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forrie (black.navinet.net [206.25.93.86]) by spook.navinet.net (8.9.2/8.9.2) with SMTP id QAA01443 for ; Mon, 1 Feb 1999 16:16:21 -0500 (EST) Message-Id: <4.1.19990201160057.009d5200@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 01 Feb 1999 16:02:27 -0500 To: freebsd-questions@FreeBSD.ORG From: Forrest Aldrich Subject: Odd behavior of BIND-8.x Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This applies to either FreeBSD-3.0 or 2.2.8. I've noticed that when the system boots, named starts... but it gets 'stuck' (for lack of an explanation), this is resolved by sending a HUP signal to it. Then it's fine. I've seen this behavior in named since 2.2.5 and I can't tell if this is named itself or something else. Has anyone else noticed this problem? Forrest To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message