https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38898 Bug ID: 38898 Summary: Cron handling tar vs. deb Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs@lists.koha-community.org Reporter: alexander.wagner@desy.de QA Contact: testopia@bugs.koha-community.org CC: aude.charillon@ptfs-europe.com, philip.orr@lmscloud.de The Koha Manual details on cron jobs required by Koha and also refers to `crontab.example` as an example how to set it up: https://koha-community.org/manual/latest/en/html/cron_jobs.html As a newbie I had the impression that I should dive into all those jobs and devise a suitable `crontab` for my instance based on the example file provided. This seems to be correct procedure if Koha gets installed from the source tar balls. Once Koha is installed from pre-complied (deb-)packages, however, a number of cron jobs are added to the system `cron` automatically by means of crontabs named `koha-common`, placed into the respective system paths `/etc/cron.*/` and one might end up with the same job more than once and probably confusing behaviour. - It would be helpful to newbies to point out the automatic setup once deb's are used - It would also be helpful to mark jobs already setup automagically in the subsequent detailed documentation of the jobs. As of 24.11 these jobs seem to be added via deb and `koha-common` crontabs (section headings refer to the path they get added). ## cron.hourly build_holds_queue automatic_checkin ## cron.d process_message_queue ## cron.daily automatic_renewals automatic_checkin expire_recalls overdue_recalls fines overdue_notices serialsUpdate membership_expiry cancel_expired_holds cleanup_database auto_unsuspend_holds merge_authorities plugins_nightly ## cron.monthly share_usage_with_koha_community -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.