From owner-freebsd-questions@FreeBSD.ORG Sat Nov 27 20:20:44 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9353016A63E for ; Sat, 27 Nov 2004 20:20:44 +0000 (GMT) Received: from shadow.wixb.com (shadow.wixb.com [65.43.82.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F59A43D67 for ; Sat, 27 Nov 2004 20:20:44 +0000 (GMT) (envelope-from jbronson@wixb.com) Organization: Aurora Health Care, Milwaukee WI USA Message-Id: <6.2.0.14.2.20041127141814.00c13fa0@cheyenne.wixb.com> Date: Sat, 27 Nov 2004 14:20:43 -0600 To: freebsd-questions@freebsd.org From: "J.D. Bronson" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: named not sending notifies? (5.3) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 20:20:44 -0000 I noticed that when named starts during boot up, I dont seem to be able to 'send' notifies to my slave machines: notify to x.y.71.63#53: retries exceeded notify to x.y.71.63#53: retries exceeded notify to x.y.71.63#53: retries exceeded However, if I pkill named and start it manually from the command line it sends notifies just fine. Has anyone else noticed this?? If it was my config, I would expect it to act like this whether or not I start it manually or not. But this is not the case. PS. How important is it to bother with this? - should I just turn off notify and let the refresh handle things? -- J.D. Bronson Aurora Health Care // Information Services // Milwaukee, WI USA Office: 414.978.8282 // Email: jd@aurora.org // Pager: 414.314.8282