[mythtv-users] Recordings off 1 Hour

[Dan Ritter]

On Tue, Apr 22, 2008 at 11:38:10PM -0500, Roger Heflin wrote:
> When a machine is shutdown properly it syncs the current time with the bios 
> clock.   If a machine crashes (after Daylight savings time has happened-without 
> a proper shutdown this of course does not happen) then when the machine comes 
> back up it is an hour off and too far for ntp to sync it and it will stay off by 
> an hour, and you get the sort of behavior  you were seeing.
> 
> It is one disadvantage to having slave backends, I started using a cron job to 
> sync things with rdate (to the master backend) as ntp is somewhat fragile and 
> takes careful monitoring (kind of painful in a home environment, not so bad for 
> enterprise environments).

Firing up my ntpd at boot time begins with running ntpdate
against a reliable time server. If you keep your configuration
simple, ntp is pretty easy:

/etc/ntpd.conf:
#----
restrict 0.0.0.0 mask 0.0.0.0 noquery
restrict 10.0.0.0 mask 255.0.0.0 nomodify
restrict 127.0.0.1 nomodify

driftfile /etc/ntp/drift
pidfile /var/lock/subsys/ntpd

server 0.us.pool.ntp.org
server 1.us.pool.ntp.org
server 2.us.pool.ntp.org
server 3.us.pool.ntp.org
#----

That will do for your master server on a 10.* net. Everything else can use:

/etc/ntpd.conf:
#----
restrict 0.0.0.0 mask 0.0.0.0 noquery
restrict 127.0.0.1 nomodify
driftfile /etc/ntp/drift
pidfile /var/lock/subsys/ntpd
server IP_OF_MASTER_NTP_SERVER
#----


-dsr-

-- 
http://tao.merseine.nu/~dsr/eula.html is hereby incorporated by reference.