home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!mintaka.lcs.mit.edu!bloom-picayune.mit.edu!athena.mit.edu!eichin
- From: eichin@athena.mit.edu (Mark W. Eichin)
- Newsgroups: comp.unix.bsd
- Subject: Re: 386bsd & timezone
- Message-ID: <EICHIN.92Sep11051611@tsx-11.mit.edu>
- Date: 11 Sep 92 09:16:16 GMT
- References: <1992Sep10.063811.3134@Saigon.COM> <STARK.92Sep10142919@sbstark.cs.sunysb.edu>
- Sender: news@athena.mit.edu (News system)
- Distribution: usa
- Organization: Massachusetts Institute of Technology
- Lines: 7
- In-Reply-To: stark@cs.sunysb.edu's message of Thu, 10 Sep 1992 19:29:19 GMT
- Nntp-Posting-Host: tsx-11.mit.edu
-
- >> My solution was just to set the CMOS information to reflect standard
- Has anyone made changes to get 386BSD to update the CMOS time
- from the kernel time? xntp3 builds and works out of the box, but if
- the CMOS time drifts far enough, at the next reboot xntpd will declare
- that "something is wrong" and won't try to fix it.
- _Mark_ <eichin@athena.mit.edu>
- MIT Student Information Processing Board
-