From owner-freebsd-current@FreeBSD.ORG Sat Aug 17 17:42:09 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BE77EC96 for ; Sat, 17 Aug 2013 17:42:09 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9A07A233F for ; Sat, 17 Aug 2013 17:42:09 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id r7HHg8N6050889; Sat, 17 Aug 2013 17:42:08 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.123] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id ux476nqrh5zakeaf86h5jzmcwn; Sat, 17 Aug 2013 17:42:07 +0000 (UTC) (envelope-from tim@kientzle.com) Subject: Re: /etc/namedb->@ referrs to NIL after crash or typing "reboot" (not shutdown -r) Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=utf-8 From: Tim Kientzle In-Reply-To: <20130817193517.2bf01dfe@thor.walstatt.dyndns.org> Date: Sat, 17 Aug 2013 10:42:07 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20130817113636.21346cd2@thor.walstatt.dyndns.org> <520FAE99.8040003@passap.ru> <20130817193517.2bf01dfe@thor.walstatt.dyndns.org> To: "O. Hartmann" X-Mailer: Apple Mail (2.1283) Cc: FreeBSD CURRENT , Boris Samorodov X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Aug 2013 17:42:09 -0000 On Aug 17, 2013, at 10:35 AM, O. Hartmann wrote: > On Sat, 17 Aug 2013 21:10:49 +0400 > Boris Samorodov wrote: >=20 >> 17.08.2013 13:36, O. Hartmann =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >>=20 >>> I can reproduceable truncate the link in /etc/ to be NIL by typing >>> simply "reboot" when rebooting the box >>=20 >> Does it make any difference if you use "shutdown -r" instead? >>=20 >=20 > Yes, when using "shutdown -r" the link isn't broken and the system > reboots and operates as expected. Only if I use the "quick and dirty > way" via "reboot" or after a crash when service named ahs already been > started the link is dead. If a crahs occurs BEFORE service named has > been started, the recovery is also operable - this is my observation. Does "reboot" show the same problem If the system has been running for a while (at least 15 minutes or so)? Your broken link sounds like the expected behavior when you do a dirty reboot shortly after the link has been created (before the link contents have been written all the way to disk). But the broken /etc/namedb link shouldn't prevent named from restarting after the reboot; maybe we should change the named startup scripts to test this link and delete/recreate it if it's broken? Tim