[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Fwd: [Debian-med-packaging] Bug#1003314: orthanc package: startlimitburst too low



Thank so much for your pointer to dpkg triggers!

The trigger was added by the following changeset in the main orthanc package:
https://salsa.debian.org/med-team/orthanc/-/commit/4ba881a9551b4cba88fb4e278957618380d790c6

I will now update the plugin packages so as they activate this new trigger.

Regards,
Sébastien-



On 14/01/22 14:04, Aaron M. Ucko wrote:
Sébastien Jodogne <s.jodogne@orthanc-labs.com> writes:

Please could someone indicate how I can modify such a postinst script
so as Orthanc is only restarted once if multiple Orthanc plugins are
installed/upgraded at once?

Please try using dpkg's trigger mechanism, per
/usr/share/doc/dpkg/triggers.txt.gz (and the manpages it cites).

Or should I modify the main "orthanc.service" to set
"StartLimitBurst=10", as proposed by Gerald? But in this case, how to
ensure the compatibility with non-systemd deployments?

Do they even have such limits?  I can't speak for alternatives that were
never the default (such as runit, or upstart if that's still an option),
but I'm fairly certain classic SysV init never attempted to track, let
alone limit, how frequently services restarted.

At any rate, thanks for checking!


Reply to: