I got a scolding once because my clock was set to CST and not GMT (for the webserver). What do most do when setting the clock for webservers? On 1 Jun 2001, at 23:33, Carl Wilhelm Soderstrom wrote: From: Carl Wilhelm Soderstrom <chrome at real-time.com> To: tclug-list at mn-linux.org Subject: Re: [TCLUG] setting time from time server Send reply to: tclug-list at mn-linux.org <mailto:tclug-list-request at mn-linux.org?subject=subscribe> <mailto:tclug-list-request at mn-linux.org?subject=unsubscribe> Date sent: Fri, 1 Jun 2001 23:33:10 -0500 > > The simpelest way I know of is to install xntp > > rdate is even simpler. :) > > I just do 'rdate -s time.nist.gov' > then do 'hwclock -w' (or 'clock -w' will work on redhat) to set the > hardware clock to the software time. > > by the look of things, it may not be as accurate as ntpdate or xntpd; > but if a few seconds is close enough for you; it's probably good > enough. :) > > I used to just have a cron job that ran once a week, and used rdate > and clock to set the system clock against time.nist.gov. it's really > not the best thing if your system clock 'drifts' pretty badly, tho. > some programs don't react well to having the system time changed out > from under them. > > for a production environment, with many machines working in close > synchronization with each other (logging to a common loghost, for > instance); xntpd is definitely the way to go. > > Carl Soderstrom. > -- > Network Engineer > Real-Time Enterprises > (952) 943-8700 > _______________________________________________ > tclug-list mailing list > tclug-list at mn-linux.org > https://mailman.mn-linux.org/mailman/listinfo/tclug-list