Date: Sat, 17 Aug 2013 10:42:07 -0700 From: Tim Kientzle <tim@kientzle.com> To: "O. Hartmann" <ohartman@zedat.fu-berlin.de> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org>, Boris Samorodov <bsam@passap.ru> Subject: Re: /etc/namedb->@ referrs to NIL after crash or typing "reboot" (not shutdown -r) Message-ID: <A89885AB-7819-4F0A-A98E-7C35394CD0A0@kientzle.com> In-Reply-To: <20130817193517.2bf01dfe@thor.walstatt.dyndns.org> References: <20130817113636.21346cd2@thor.walstatt.dyndns.org> <520FAE99.8040003@passap.ru> <20130817193517.2bf01dfe@thor.walstatt.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 17, 2013, at 10:35 AM, O. Hartmann wrote: > On Sat, 17 Aug 2013 21:10:49 +0400 > Boris Samorodov <bsam@passap.ru> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A89885AB-7819-4F0A-A98E-7C35394CD0A0>