I would actually suggest running ntpd on it, yes, it seems excessive for an ltsp client (but remember how much is actually running on a client) And it does a much better job at getting the time set correctly. Not to mention that rdate doesn't know if the time it is getting from the server is accurate, ntp is accurate usually to .001s. Finally, the big difference is that ntp when setup correctly, will check against many servers, whereas rdate can only do one
there are devices that require that kind of accuracy, although LTS isn't one of them. Also, tomorrow night (Friday 7 February 2003 at 7pm at Yorktown High School in Arlington, there is a LUG that is meeting, they have a running LTS Lab and a bunch of guys that could answer your questions in person. Jason On Thu, 2003-02-06 at 11:17, Jameson C. Burt wrote: > I use the LTSP webcam package, ltspwebcam, > which displays a picture having a machine date, because of a setting in > /opt/ltsp/i386/usr/local/share/camserv.cfg > This displayed date can be useful since webcams apparently > retain a few images sometimes hours old. > SO, WHAT APPROACH WOULD YOU TAKE TO SETTING DATE? > > Here are some approaches I consider. > 1. rdate > I lean towards this approach, which would run on bootup of the LTS, > rdate my-main-computer > Presuming I use this approach, would I then best add > /opt/ltsp/i386/sbin/rdate #a 5 kilobyte file > and append to > /opt/ltsp/i386/etc/rc.local > the line > /sbin/rdate my-main-computer > > 2. ntp (Network Time Server); in particular, ntpdate. > I decided not to use this since, for a LTS, > it's excessive in software installation, > and either external networking must be up, or my main computer must > run an ntpd daemon. > > 3. ??? What haven't I thought of? > > 4. This is a crazy idea that merely makes things more complex. > > > The Jammin 125 I got 4 weeks ago has a date differing by two hours > (I'm EST, and it must be MST). > I could probably add > /opt/ltsp/i386/sbin/hwclock > then permanently change my LTS hardware clock. > But this approach isn't as robust as an approach like "rdate", > which (hopefully) properly changes date even when the LTS clock > runs low, and once setup, > this approach needn't be applied by hand to each LTS. > > > I welcome any suggestions. -- ############################################################################## # Jason Straw -- [EMAIL PROTECTED] -- Freenode and GOVIA, Media for the Future # # Freenode Radio -- Webmaster, Head Engineer # # Freenode IRC -- staff member # # OSEF -- Project Impresario of GOVIA # # GPG Key ID -- pgp.mit.edu -- D662C649 # ##############################################################################
signature.asc
Description: This is a digitally signed message part
