Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!olivea!charnel!psgrain!ee.und.ac.za!ucthpx!casper.cs.uct.ac.za!gimli!root From: root@gimli.cs.uct.ac.za (Sandi Donno) Subject: Re: fsck summary info bad after every shutdown Message-ID: <root.737990482@gimli> Sender: news@cs.uct.ac.za (news) Organization: Computer Science Department, University of Cape Town References: <root.737640955@gimli> <1993May19.095416.21213@email.tuwien.ac.at> Date: Fri, 21 May 1993 13:21:22 GMT Lines: 18 In <1993May19.095416.21213@email.tuwien.ac.at> mbirgmei@email.tuwien.ac.at (Martin BIRGMEIER) writes: >This happens if you set the clock (via rdate, for example) from a >remote machine after multiuser bootup, and the local (i.e. system board) >clock is late (this is what happened to me). >Solution: >Set your CMOS clock ahead, or use some other means to keep it within a >few seconds (the time to run the reboot sequence, to be precise) within >the network time. Martin Thanks! This was indeed my problem. These machines are all running xntpd, so the clock is getting changed after bootup. -- Sandi Donno