[mythtvnz] Timesync via Sat.
Noel & Di
mythtvnz@lists.linuxnut.co.nz
Fri, 01 Jun 2007 11:46:58 +1200
This is a multi-part message in MIME format.
--------------090006070900080700040008
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Nick Rout wrote:
>On Fri, June 1, 2007 8:56 am, Noel & Di wrote:
>
>
>>Andrew Ruthven wrote:
>>
>>
>>
>>>On Thu, 2007-05-31 at 04:35 +1200, Noel & Di wrote:
>>>
>>>
>>>
>>>
>>>>I am struggling to get my crontab entry to work
>>>>After creating a crontab.txt file of
>>>>0 * * * * /usr/bin/dvbdate --set
>>>>and invoking
>>>>crontab crontab.txt
>>>>I get a message "unable to set time: Operation not permitted.
>>>>What am I doing wrong??
>>>>
>>>>
>>>>
>>>>
>>>Slightly silly question perhaps, but is this in roots crontab?
>>>If you are, can you run `dvbdate --set` from the command line as root
>>>okay?
>>>
>>>Cheers!
>>>
>>>
>>>
>>>
>>>
>>The -- force option works!!
>>Thanks for that.
>>
>>
>
>If it needs --force every time then your system time is drifting more than
>1800 secs (30 mins) between settings, which means something is seriously
>wrong.
>
>One thing is that your clock might not be getting set right on
>shutdown/startup. The mechanism for saving the system clock into the
>hardware clock correctly (so that the hardware clock correctly sets the
>system clock) varies per distro, but it is pretty important to get it
>right.
>
>On a system that runs solely on linux (and I'm guessing no one is running
>mythtv dual boot with windows) it is easiest to set the hardware clock to
>UTC (GMT). The system clock runs on UTC anyway, and the translation to
>your local timezone is done via /etc/localtime, or the TZ environment
>variable.
>
>But anyway, enough detail, if you need --force each time you update,
>something is wrong
>
>
Hi Nick
Thanks for all that, I'm running a dedicated knoppmyth box & the time
was initially out by several hours as a result of various fiddlings by
me. Used --force the first time only & --set generates no errors now.
Normally this box has reasonable time keeping accuracy. A tier 1 system
- except where I've fiddled & tweaked. It's an old PC Chips board (pre
'92 BIOS), 1.8GHz Athlon , 512 sheep, 250Gb HDD and R5F1 clean install.
The poor thing has had a hard life & the on-board USB died after me
powering things that just should NOT get powered from the USB, *lol* -
have a MCEUSB remote, so I made a serial IR receiver & eventualy figured
out (With help from the forums) to use irrecord & re assign key names
in lircd - all works well now. Currently scrounging for a new
motherboard so I can use ACPI wakeup - of whick I know little. An old
DOS hound from waaay back, Linux is new to me & quite exciting.
--------------090006070900080700040008
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Nick Rout wrote:
<blockquote
cite="mid13162.219.89.81.142.1180647397.squirrel@rout.dyndns.org"
type="cite">
<pre wrap="">On Fri, June 1, 2007 8:56 am, Noel & Di wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
Andrew Ruthven wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Thu, 2007-05-31 at 04:35 +1200, Noel & Di wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I am struggling to get my crontab entry to work
After creating a crontab.txt file of
0 * * * * /usr/bin/dvbdate --set
and invoking
crontab crontab.txt
I get a message "unable to set time: Operation not permitted.
What am I doing wrong??
</pre>
</blockquote>
<pre wrap="">Slightly silly question perhaps, but is this in roots crontab?
If you are, can you run `dvbdate --set` from the command line as root
okay?
Cheers!
</pre>
</blockquote>
<pre wrap="">The -- force option works!!
Thanks for that.
</pre>
</blockquote>
<pre wrap=""><!---->
If it needs --force every time then your system time is drifting more than
1800 secs (30 mins) between settings, which means something is seriously
wrong.
One thing is that your clock might not be getting set right on
shutdown/startup. The mechanism for saving the system clock into the
hardware clock correctly (so that the hardware clock correctly sets the
system clock) varies per distro, but it is pretty important to get it
right.
On a system that runs solely on linux (and I'm guessing no one is running
mythtv dual boot with windows) it is easiest to set the hardware clock to
UTC (GMT). The system clock runs on UTC anyway, and the translation to
your local timezone is done via /etc/localtime, or the TZ environment
variable.
But anyway, enough detail, if you need --force each time you update,
something is wrong
</pre>
</blockquote>
Hi Nick<br>
Thanks for all that, I'm running a dedicated knoppmyth box & the
time was initially out by several hours as a result of various
fiddlings by me. Used --force the first time only & --set
generates no errors now. Normally this box has reasonable time keeping
accuracy. A tier 1 system - except where I've fiddled & tweaked.
It's an old PC Chips board (pre '92 BIOS), 1.8GHz Athlon , 512 sheep,
250Gb HDD and R5F1 clean install. The poor thing has had a hard life
& the on-board USB died after me powering things that just should
NOT get powered from the USB, *lol* - have a MCEUSB remote, so I made a
serial IR receiver & eventualy figured out (With help from the
forums) to use irrecord & re assign key names in lircd - all works
well now. Currently scrounging for a new motherboard so I can use ACPI
wakeup - of whick I know little. An old DOS hound from waaay back,
Linux is new to me & quite exciting.<br>
</body>
</html>
--------------090006070900080700040008--