.\" Automatically generated by Pod::Man 4.10 (Pod::Simple 3.35) .\" .\" Standard preamble: .\" ======================================================================== .de Sp \" Vertical space (when we can't use .PP) .if t .sp .5v .if n .sp .. .de Vb \" Begin verbatim text .ft CW .nf .ne \\$1 .. .de Ve \" End verbatim text .ft R .fi .. .\" Set up some character translations and predefined strings. \*(-- will .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left .\" double quote, and \*(R" will give a right double quote. \*(C+ will .\" give a nicer C++. Capital omega is used to do unbreakable dashes and .\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff, .\" nothing in troff, for use with C<>. .tr \(*W- .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p' .ie n \{\ . ds -- \(*W- . ds PI pi . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch . ds L" "" . ds R" "" . ds C` "" . ds C' "" 'br\} .el\{\ . ds -- \|\(em\| . ds PI \(*p . ds L" `` . ds R" '' . ds C` . ds C' 'br\} .\" .\" Escape single quotes in literal strings from groff's Unicode transform. .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. .\" .\" Avoid warning from groff about undefined register 'F'. .de IX .. .nr rF 0 .if \n(.g .if rF .nr rF 1 .if (\n(rF:(\n(.g==0)) \{\ . if \nF \{\ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . if !\nF==2 \{\ . nr % 0 . nr F 2 . \} . \} .\} .rr rF .\" ======================================================================== .\" .IX Title "DH_SYSTEMD_START 1" .TH DH_SYSTEMD_START 1 "2021-03-06" "13.3.3~bpo10+1" "Debhelper" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l .nh .SH "NAME" dh_systemd_start \- start/stop/restart systemd unit files .SH "SYNOPSIS" .IX Header "SYNOPSIS" \&\fBdh_systemd_start\fR [\fIdebhelper options\fR] [\fB\-\-restart\-after\-upgrade\fR] [\fB\-\-no\-stop\-on\-upgrade\fR] [\fIunit file\fR ...] .SH "DESCRIPTION" .IX Header "DESCRIPTION" \&\fBdh_systemd_start\fR is a debhelper program that is responsible for starting/stopping or restarting systemd unit files in case no corresponding sysv init script is available. .PP As with \fBdh_installinit\fR, the unit file is stopped before upgrades and started afterwards (unless \fB\-\-restart\-after\-upgrade\fR is specified, in which case it will only be restarted after the upgrade). This logic is not used when there is a corresponding SysV init script because invoke\-rc.d performs the stop/start/restart in that case. .SH "OPTIONS" .IX Header "OPTIONS" .IP "\fB\-\-restart\-after\-upgrade\fR" 4 .IX Item "--restart-after-upgrade" Do not stop the unit file until after the package upgrade has been completed. This is the default behaviour in compat 10. .Sp In earlier compat levels the default was to stop the unit file in the \&\fIprerm\fR, and start it again in the \fIpostinst\fR. .Sp This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon will not get confused by the package being upgraded while it's running before using this option. .IP "\fB\-\-no\-restart\-after\-upgrade\fR" 4 .IX Item "--no-restart-after-upgrade" Undo a previous \fB\-\-restart\-after\-upgrade\fR (or the default of compat 10). If no other options are given, this will cause the service to be stopped in the \fIprerm\fR script and started again in the \fIpostinst\fR script. .IP "\fB\-r\fR, \fB\-\-no\-stop\-on\-upgrade\fR, \fB\-\-no\-restart\-on\-upgrade\fR" 4 .IX Item "-r, --no-stop-on-upgrade, --no-restart-on-upgrade" Do not stop service on upgrade. .IP "\fB\-\-no\-start\fR" 4 .IX Item "--no-start" Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a corresponding init script). .SH "NOTES" .IX Header "NOTES" Note that this command is not idempotent. \fBdh_prep\fR\|(1) should be called between invocations of this command (with the same arguments). Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts. .PP Note that \fBdh_systemd_start\fR should be run after \fBdh_installinit\fR so that it can detect corresponding SysV init scripts. The default sequence in \fBdh\fR does the right thing, this note is only relevant when you are calling \&\fBdh_systemd_start\fR manually. .SH "SEE ALSO" .IX Header "SEE ALSO" \&\fBdebhelper\fR\|(7) .SH "AUTHORS" .IX Header "AUTHORS" pkg\-systemd\-maintainers@lists.alioth.debian.org