While waiting for an answer on why the crontab
event was not running something interesting happened: the script setup through crontab
actually ran! It turns out that it seems to to be using the time of day without considering the summer time. That is, it is taking the time as a fixed time from UTC not considering that it is still summer time.
As an example, the task that was setup as:
52 13 * * * /home/username/my_script.sh
actually ran at 14:52 (that is what the clock at the top right corner of my screen said). Because we are still in summer time, I am concluding that cron
actually looks at the system clock and ignores the fact that we have added one hour due to summer time. Using @Rohitt Vashishtha words: cron doesn't play nice with timezones.
sudo crontab -u username -r
to delete what I had.Then
sudo crontab -u username -e
to create and edit a newcrontab
forusername
. At the end of the filed I added:
– Juan Antonio Oct 24 '16 at 16:5852 13 * * * DISPLAY=:0 firefox
. I added this at 13:50 my time but at 13:52 nothing happened.crontab
actually ran! It turns out that it seems to to be using the time of day without considering the summer time. That is, it is taking the time as a fixed time from UTC not considering that it is still summer time.The issue about not being able to install
– Juan Antonio Oct 24 '16 at 18:45gnome-schedule
still remains. I recognise this is a different issue so I will be removing this from here and asking this in a different question.