[Gambas-user] Crontab and Gambas executable
bagonergi at gmail.com
Mon Dec 21 19:52:13 CET 2020
Il giorno lun 21 dic 2020 alle ore 18:33 Jesus Guardon <ea7dfh at ea7dfh.com>
Hello Jesus, happy to hear from you
> Don't know if it matters, but which file are you editing? /etc/crontab?
> yes, with the 'crontab -e' command
It seems to me it's much better to add a new file in any of these
> folders, depending on your needs:
> /etc/cron/hourly , etc
i don't understand, i am a newbie from linux ;-D
> Also, be sure you left no spaces or blank lines at the beginning of your
> cron file, being or not comments as #my cron file
> If none of the above works for you, try to add the system path above
> your cron command:
> PATH=/usr/bin:/usr/local/bin: and so on.
I have done many tests, here is the last + my PATH :
# Edit this file to introduce tasks to be run by cron.
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
# and what command to run for the task
# To define the time you can provide concrete values for
# minute (m), hour (h), day of month (dom), month (mon),
# and day of week (dow) or use '*' in these fields (for 'any').
# Notice that tasks will be started based on the cron's system
# daemon's notion of time and timezones.
# Output of the crontab jobs (including errors) is sent through
# email to the user the crontab file belongs to (unless redirected).
# For example, you can run a backup of all your user accounts
# at 5 a.m every week with:
# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
# For more information see the manual pages of crontab(5) and cron(8)
# crontab Environmental settings
# Crontab Command settings
# m h dom m dow command
28 19 * * * gedit
29 20 * * * killall -w gedit
Thank you and regards
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the User