Crontab problem....??

[Skywatch]

Aha! - Good question.

$date shows the clock at GMT and not BST, so that might be the cause of the tests failing, I guess something happened going back to wheezy when I got no sound from the Jessie upgrade (will be trying that again in a day or two)......

However, would a wrong time setting also stop the @reboot cron job running correctly beacuse here we have no time parameters at all?

I have been editing as Xbian with just 'crontab -e' but using 'sudo nano /etc/crontab' - so will try again this afternoon/evening as root, I have a lot of other things that need doing now

I have a spare DS3231 hardware clock board and will add it later on today if I get time.

Ironically, that cron job I set up on Raspbian is to sync the DS3231 with NTP at reboot or once a week!

UPDATE...

It's started working! - I don't know why, I was having a problem getting the i2c HWclock to work (looks like an 'iffy' module, have ordered more) but when I got as far as I could with that I checked my emails and there they were, lots of reboot messages from the work on i2c! - Odd.

UPDATE 2 ...
I also got rid of the annoying email from Python. Just add ">/dev/null 2>&1" without the quotes after the crontab entry and ta-da! = No more emails from that!
I will look into doing the same with the 'daily' message when I find it!

Thanks for the help and pointing me in the right direction! - I have learned some new stuff this week!