Warped Clock

[dyrplq]

To automatically get over the warped clock issue (see here for details; http://minnie.tuhs.org/twiki/bin/vie...veNoGuideData), I've added the following to Crontab;

#warped clock fix
05 01 * * * 7 touch /var/timestamp
06 01 * * * 7 /hack/bin/force_index.tcl

however this doesn't appear to be making any difference. The cronlog shows that it has run but I still get warped clock unless I manually run the above via a command line. Any ideas why this doesn't work in Cron?

Ta, Phil

[catdog]

I'm not much of a linux user, but the "7" looks very out of place to me. There should only be 5 entries to specify the date/time to run (you have 6), and the last entry is the day of the week from 0-6 (so 7 could never occur).

Personally I have
10 02 * * sat touch /var/timestamp

which occurs on saturday at 2:10am, which reports in the cron log as
CMD (touch /var/timestamp)

[petestrash]

I agree with catdog, drop the seven's.

But really you should not be having any warped clock issues if your image is later than April 18 2005, and your tivo is making successful daily calls.

If your image is pre 19/4/05 then there is a known bug and the wrong ntpdate file was included.

You can correct this by downloading the correct file.

Method 1:
Download http://minnie.tuhs.org/twiki/pub/Upl...ebHome/ntpdate and replace the existing file in /bin using FTP.

Method 2:
Enter the following into your telnet client:

cd /bin
rw
mv ntpdate ntpdate.old
wget http://131.244.9.101/twiki/pub/Uploads/WebHome/ntpdate
ro

Peter

[dyrplq]

Thanks guys. I had 7 for "7 days of the week" ie, every day. Obviously not right.

[zollymonsta]

I don't think you should need to run those commands via a crontab either.
Usually if you run it once it doesn't re-appear again (unless something does go awry).

ZollyMonsta