https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36229
David Nind <da...@davidnind.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Text to go in the|This fixes the order of the |This fixes the order of the
release notes|daily cron jobs |daily cron jobs
|(/etc/cron.daily/koha-commo |(/etc/cron.daily/koha-commo
|n) so that koha-run-backups |n) so that koha-run-backups
|is run first.
|is run first.
|
|
|Reasons for |Reasons for
|this include:
|this include:
|
|
|1. The |1. The
|koha-run-backups cron job |koha-run-backups cron job
|takes a backup before |takes a backup before
|running scripts that change |running scripts that change
|database contents. If there |database contents. If there
|is a problem with those |is a problem with those
|scripts, you'll have a very |scripts, you'll have a very
|recent backup on which to |recent backup on which to
|fallback.
|fallback.
|
|
|2. It's a |2. It's a
|resource intensive job. If |resource intensive job. If
|you have a lot of Koha |you have a lot of Koha
|instances, this means |instances, this means
|you're running your most |you're running your most
|intensive job at the end of |intensive job at the end of
|the job run, which might be |the job run, which might be
|a lot later in the day than |a lot later in the day than
|you anticipate. (Of course, |you anticipate. (Of course,
|you can update /etc/crontab |you can update /etc/crontab
|to change when |to change when
|/etc/cron.daily is run, but |/etc/cron.daily is run, but
|this will help reduce |this will help reduce
|impact in the meantime.) |impact in the meantime.)
| |
| |Deployment of this change:
| |- New installations: This
| |change will seamlessly
| |apply for new
| |installations.
| |- Existing
| |installations:
| | . You
| |HAVEN'T manually modified
| |the crontab: it will
| |seamlessly apply.
| | . You
| |HAVE manually modified the
| |crontab: you will be
| |prompted, and will need to
| |decide about applying the
| |change.
| | . Where
| |deployment tools are used
| |(such as Ansible): this
| |will depend on what tools
| |you use and how they are
| |configured.
--- Comment #7 from David Nind <da...@davidnind.com> ---
(In reply to David Cook from comment #6)
> (In reply to David Nind from comment #5)
> > I've added a release note, but a quick question: Will this change only fix
> > this for new installations?
> >
> > If it does, I'll add a note that this change will need to be made manually
> > for existing installations.
>
> It's complicated.
>
> It will seamlessly apply for new installations, it will seamlessly apply for
> existing installations where the crontab hasn't been previously manually
> modified.
>
> For existing installations where the crontab has been previously manually
> modified, sysadmins will be prompted to decide whether or not to apply the
> change. (Deployment tools like Ansible are often set to automatically accept
> changes, so automated deployments often will apply the change, but it will
> vary by individual implementation.)
Thanks for the great explanation David! I've updated the release note to
hopefully reflect this.
--
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
Koha-bugs@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
