On Thursday, November 21, 2002, at 01:30 AM, Martin Edenhofer wrote:

In $OTRS_HOME/var/cron/* are all cron jobs for the otrs user located.

Its better to do the changes there, because on the next otrs-cron-reload
(bin/Cron.sh start) your changes of (crontab -e otrs...) are lost.
Aren't the files there overwritten when someone upgrades? :)

I can't find anything that references otrs-cron-reload in the distribution, is that new in CVS?

I didn't use the bin/Cron.sh script because it's hardcoded to use #!/bin/bash, which doesn't exist on my system. And the arguments to crontab are different on my system (you have 'crontab $CRON_USER $CRON_TMP_FILE' - with the crontab command in FreeBSD (all BSDs?) this would need to be 'crontab -u $CRON_USER $CRON_TMP_FILE', unless you're running it as the otrs user in which case it's just 'crontab $CRON_TMP_FILE').

BTW, I notice bin/Cron.sh uses /tmp for it's temporary file instead of $HOME/var/tmp - why is that?

Bryan

_______________________________________________
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs


Reply via email to