hi mr-b,
Yes it is that easy. To summarize. 1. Run ntpd once at boot. This assumes that there is a working network that can access a time server on the internet. This is how TinyCore/piCore/piCorePlayer works by default. This works fine 99% of the time. Possible issues: - time drifts of a couple of seconds a day - network problem prevents ntpd working - firewall blocks ntp - power failure happens and piCorePlayer boots faster than router - using local ntp server (fixed by setting ntpserver bootcode) 2. Use cron to run ntpd. This is usually used when ntpd has worked ok during boot process but you are concerned about the time drift. So usually once a day, late a night, ntpd is run to sync time. cron could be run run more often if you wanted too. This won't fix a epoch time issue until the designated cron job time. Once we started using LMS on piCorePlayer accurate time setting became a little more important. Also, if you are using the clock display in Jivelite it would be nice if the time was accurate. 3. Run ntpd as a daemon. That's what the "d" stands for. Most computer system would to this. Local ntpd program negotiates with time server to work out a suitable schedule to minimise load. Why doesn't piCorePlayer just use option 3 and be done with it? Feature creep and bloat! TinyCore/piCore uses option 1. TinyCore/piCore is supposed to be a minimal system. If we keep adding to it, it will eventually be like any other distribution. regards Greg ------------------------------------------------------------------------ Greg Erskine's Profile: http://forums.slimdevices.com/member.php?userid=7403 View this thread: http://forums.slimdevices.com/showthread.php?t=112335 _______________________________________________ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
