Bug#831002: Please use restart-after-upgrade

[Michael Biebl]

Package: rpcbind
Version: 0.2.3-0.5
Severity: normal
Tags: patch

Hi,

please consider using --restart-after-upgrade for
dh_installinit/dh_systemd_enable. Atm, the service is stopped in prerm
and started in postinst. This means there can be a pretty long downtime
during dist upgrades. With socket activation, which is used in systemd,
this doesn't work particularly well, as any incoming request could
trigger a start during upgrades.
--restart-after-upgrade fixes that nicely.

With debhelper compat level 10, --restart-after-upgrade will become the
default behaviour. So once you switch to that compat level, you can drop
this patch again.

Thanks for considering.

Michael


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages rpcbind depends on:
ii  init-system-helpers  1.40~1.gbpee156d
ii  libc6                2.23-1
ii  libsystemd0          230-7
ii  libtirpc1            0.2.5-1
ii  libwrap0             7.6.q-25
ii  lsb-base             9.20160629

rpcbind recommends no packages.

rpcbind suggests no packages.

-- no debconf information
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Use-restart-after-upgrade.patch
Type: text/x-diff
Size: 788 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20160713/71008856/attachment.patch>