[Koha-bugs] [Bug 1993] Task Scheduler Needs Re-write

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1993

Galen Charlton <gmcharlt at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gmcharlt at gmail.com

--- Comment #34 from Galen Charlton <gmcharlt at gmail.com> ---
(In reply to comment #33)
> This brings me to a more important question: Should we encourage Koha users
> to allow login for apache user to make use of the Task Scheduler? Note that
> is a general Apache hardening measure to not allow interactive login for the
> apache user. IMO we (as Koha developers) should not stimulate Koha users to
> lower security barriers to enable Koha functionality.

I agree: we should not be asking users to grant special privileges to the user
that Apache runs as,

> Another approach to the Task Scheduler could be to have a specific cronjob,
> look for Koha reports to run at specified times without allowing apache to
> add generic jobs with all security risks attached..

I think writing a cronjob (and abandoning Schedule::At) is the way to go.  In
particular, I suggest the following implementation:

- create a database table to store a queue of reports to run (or maybe
generalize it a bit and call it a job queue table)
- the current report scheduling functionality would just add rows to the queue
with a run start time set by the user
- the cronjob would periodically check the queue and run any pending reports
whose run start time has passed

This would be pretty light-weight, but would allow us to get fancier in the
future.  For example, adding functionality to schedule reports to run
periodically could be done by writing code to add entries into the job queue.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are watching all bug changes.