I used your first example, and it worked out fine. ?I¡¯ve got my Qnet gateway setup to run the YSFHostupdate.sh script every night at midnight, and so far I¡¯ve not seen any errors in the system logs thus far, so all seems to be working as it should. ?Don¡¯t worry about the voiceover thing, it works 95% of the time, but sometimes some syntax causes it to get a bit flaky. ?Kind of ironic that it doesn¡¯t really have a lot of smarts to work well in terminal, and terminal is just simply a flat text-based screen with nothing but ansi characters, that should not need some kind of special call to some API to let voiceover know that a given event has occurred. ?This has been good, it¡¯s made me a bit more competent in Linux, so all is not lost.
toggle quoted message
Show quoted text
First off, let me apologise.? I apparently passed over your previous mentions of VoiceOver and did not realise until now that you have been using it to read what I have been posting.? I probably could have been a little more careful to make sure it would render properly for you.
There are two ways to setup a job to run at midnight in crontab:
0?? 0?? *?? *?? *?? /path/to/job.sh
In order, those figures are the first minute - in the first hour - of every calendar day - of every month - on every weekday - and the full path to the job.
If your system is running on a Raspberry Pi and your user name is 'pi,' the this would be your crontab entry to update ysfhosts.txt every day at midnight would be:
0?? 0?? *?? *?? *? /home/pi/YSFClients/YSFGateway/YSFHostsupdate.sh
There is also a shorthand for a daily job at midnight.? '@daily' can replace the entire scheduling portion of the line, like this:
@daily???? /home/pi/YSFClients/YSFGateway/YSFHostsupdate.sh
