We've done something like that, here, using plugins to do anything we needed. The reason we never published it was that it was not secure _at all_ and we needed to revisit it. Do you intend to "hardcode" the jobs available, or leave the user to decide, thus opening your backend to some unwelcomed behavior? I suppose that if you limit it to running tasks under you hierarchy/misc/cronjobs, that would work just fine, even if being somewhat limited. curious Philippe Blouin, Responsable du développement informatique Tél. : (888) 604-2627 philippe.blouin@inLibro.com <mailto:philippe.blouin@inLibro.com> inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com> On 10/27/2015 06:20 AM, Julian Maurice wrote:
Hi,
Comments in bug 1993 state that using 'at' for task scheduling is bad for security.
Galen suggests (comment 34) to use a DB table to store a list of jobs, and check periodically this list with a script in crontab.
I would like to know if someone is already working on something like that (I didn't find anything in Bugzilla). If not, do you agree with Galen's proposal as a replacement for the task scheduler ? Do you have better ideas ?