Feature #39939
closed
Scheduler: Allow execution using "at"-daemon
Added by Stefan Neufeind over 12 years ago.
Updated over 7 years ago.
Description
An alternative to regularly executing the scheduler via cron is now to execute it by using the "at"-daemon. That daemon allows the scheduler to reschedule its next invocation by a simple command. If "at" is available on the system and allowed to be used by the webserver-user enabling this new mode allows to use the scheduler without further configuration. Invocations will be automatically scheduled using at according to the activated scheduler-jobs. Changing or disabling jobs will automatically reschedule the next invocation as needed.
To activate simply set "useAtdaemon" to 1 in settings of the scheduler-plugin. Make sure the at-daemon is available and suffient rights for using it exist.
I guess "Core API" (though it has something to do with "interfacing with the outside world") is not right for documentation for the scheduler. Please move this doc-issue to an appropriate subproject/category.
- Project changed from 1106 to 739
- Target version deleted (
6.0)
Indeed, this belongs to the Scheduler's manual, so it is still a Scheduler issue.
- Target version set to 6.0.0
Duplicate of #34227 imho and can be closed?
Should not be closed because #34227 did not include documentation unfortunately.
- Category set to scheduler
- Project changed from 739 to TYPO3 Core
- Category changed from scheduler to scheduler
What kind of documentation is needed to close this issue?
Needs explanation of what "at" is, in which regard it is different to a classic "cron" and how to set it up.
On a quick search through the docs I haven't even found documentation on the scheduler, especially explaining cronjobs. But I expect that's documentated somewhere already?
In case "at" is available on your system (most systems imho have it) using at you can simply start. From run to run the job will schedule a new job for when it will need to execute next. In case you use cron, you'll usually call it every 5 minutes even if later maybe it turns out that inside the scheduler you deactivated your jobs or set them to once an hour. With "at" TYPO3 has the possibility to reschedule the next invocation to fit when it really needs to be called next time.
- Target version deleted (
6.0.0)
Just for the record: This feature is already there since at least 6.2 or something. Afaik this issue was planned to add documentation!
- Status changed from New to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by