Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
I actually manually set the date time. ntpdate was rejecting the servers I gave it. On 4 Apr 2002 at 12:19, Derek Atkins wrote: > Yea.. ntpd will refuse to adjust your clock if it's too far gone when > it starts. The fix is to run ntpdate before running ntpd. Red Hat > does this automatically if you populate /etc/sysconfig/<something> > with the list of hosts to try at startup. See /etc/rc.d/init.d/ntp > for more information. > > -derek > > Frank Ramsay <fjr at marsdome.myip.org> writes: > > > I had this problem for a while, my issue was the clock was too far off and > > ntpd refused to reset the time. I don't know if this is your problem or not, > > but setting the time manually seemed to get ntpd running. > > > > -fjr > > > > > > _______________________________________________ > > Discuss mailing list > > Discuss at blu.org > > http://www.blu.org/mailman/listinfo/discuss > > -- > Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory > Member, MIT Student Information Processing Board (SIPB) > URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH > warlord at MIT.EDU PGP key available > _______________________________________________ > Discuss mailing list > Discuss at blu.org > http://www.blu.org/mailman/listinfo/discuss -- Jerry Feldman <gaf at blu.org> Associate Director Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |