1DH_SYSTEMD_START(1)                Debhelper               DH_SYSTEMD_START(1)
2
3
4

NAME

6       dh_systemd_start - start/stop/restart systemd unit files
7

SYNOPSIS

9       dh_systemd_start [debhelper options] [--restart-after-upgrade]
10       [--no-stop-on-upgrade] [unit file ...]
11

DESCRIPTION

13       dh_systemd_start is a debhelper program that is responsible for
14       starting/stopping or restarting systemd unit files in case no
15       corresponding sysv init script is available.
16
17       As with dh_installinit, the unit file is stopped before upgrades and
18       started afterwards (unless --restart-after-upgrade is specified, in
19       which case it will only be restarted after the upgrade).  This logic is
20       not used when there is a corresponding SysV init script because
21       invoke-rc.d performs the stop/start/restart in that case.
22

OPTIONS

24       --restart-after-upgrade
25           Do not stop the unit file until after the package upgrade has been
26           completed.  This is the default behaviour in compat 10.
27
28           In earlier compat levels the default was to stop the unit file in
29           the prerm, and start it again in the postinst.
30
31           This can be useful for daemons that should not have a possibly long
32           downtime during upgrade. But you should make sure that the daemon
33           will not get confused by the package being upgraded while it's
34           running before using this option.
35
36       --no-restart-after-upgrade
37           Undo a previous --restart-after-upgrade (or the default of compat
38           10).  If no other options are given, this will cause the service to
39           be stopped in the prerm script and started again in the postinst
40           script.
41
42       -r, --no-stop-on-upgrade, --no-restart-on-upgrade
43           Do not stop service on upgrade.
44
45       --no-start
46           Do not start the unit file after upgrades and after initial
47           installation (the latter is only relevant for services without a
48           corresponding init script).
49

NOTES

51       Note that this command is not idempotent. dh_prep(1) should be called
52       between invocations of this command (with the same arguments).
53       Otherwise, it may cause multiple instances of the same text to be added
54       to maintainer scripts.
55
56       Note that dh_systemd_start should be run after dh_installinit so that
57       it can detect corresponding SysV init scripts. The default sequence in
58       dh does the right thing, this note is only relevant when you are
59       calling dh_systemd_start manually.
60

SEE ALSO

62       debhelper(7)
63

AUTHORS

65       pkg-systemd-maintainers@lists.alioth.debian.org
66
67
68
6912.6.1                            2019-10-08               DH_SYSTEMD_START(1)
Impressum