*sigh* This approach really makes it tedious to do comprehensive/predictive monitoring of the OTRS services from a central point. Do you *really* need to invent your own job scheduler? Yes, there are limitations to cron, but it’s one big piece of scripting to get Yet Another Workload Scheduler tied into a decent monitor.
Also please consider that OTRS 5 will not use all the CronJobs as OTRS 4 and before, a new Scheduler daemon will take care to handle all this repetitive tasks like close pending tickets, escalations, delete old cache and sessions, etc. Only the a CronJob to make sure the Scheduler and other daemons are running will be executed.
_______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
