From owner-freebsd-current Sun Mar 31 23:22:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA05108 for current-outgoing; Sun, 31 Mar 1996 23:22:06 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA05099 for ; Sun, 31 Mar 1996 23:21:56 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA02601 for ; Mon, 1 Apr 1996 09:21:49 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id JAA04569 for freebsd-current@FreeBSD.org; Mon, 1 Apr 1996 09:21:48 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.4/8.6.9) id JAA04226 for freebsd-current@FreeBSD.org; Mon, 1 Apr 1996 09:20:41 +0200 (MET DST) From: J Wunsch Message-Id: <199604010720.JAA04226@uriah.heep.sax.de> Subject: Re: adjkerntz (was: cvs commit: src/usr.sbin/tzsetup ...) To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 1 Apr 1996 09:20:40 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199604010045.EAA01805@astral.msk.su> from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Apr 1, 96 04:45:37 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= wrote: > > Like /usr/sbin/rmt, or /usr/share/misc/terminfo, you mean? :-) > Missing or corrupting or hanging on (via NFS) any of those files not > critical, but missing/corrupting/hanging on /etc/localtime is very > critical, because even RTC clock can be corrupted. Huh? Perhaps only when adjkerntz is running? It is never running on ``serious'' machines. ;-) Btw., there have been many problem reports about bogus adjkerntz activities here in Germany yesterday. (We had a DST switchover.) I can't tell you what exactly it has been (i don't use it myself, all my CMOS clocks run UTC), but the pattern seems to be consistent among the German users. Ah, minute... that's from the de-freebsd lists: Mar 31 04:01:00 zit1 adjkerntz[23396]: Nonexistent local time -- will retry afte r 1800 secs Mar 31 04:31:00 zit1 adjkerntz[23396]: Nonexistent local time -- will retry afte r 1800 secs Mar 31 04:31:00 zit1 adjkerntz[23454]: Nonexistent local time -- will retry afte r 1800 secs Mar 31 05:01:00 zit1 adjkerntz[23396]: Nonexistent (final) local time -- will re try after 1800 secs Mar 31 05:01:00 zit1 adjkerntz[23454]: Nonexistent (final) local time -- will re try after 1800 secs Mar 31 05:31:00 zit1 adjkerntz[23396]: Nonexistent (final) local time -- will re try after 1800 secs Mar 31 05:31:00 zit1 adjkerntz[23454]: Nonexistent (final) local time -- will re try after 1800 secs -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)