Your message dated Sat, 15 Mar 2025 13:19:24 +0100
with message-id <[email protected]>
and subject line Re: Bug#844178: Better systemd integration
has caused the Debian Bug report #844178,
regarding Better systemd integration
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
844178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844178
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: exim4
Version: 4.88~RC4-2
Severity: normal
Hi,
having a native systemd service for exim4 would be great. The sysv init
script does a *lot* of stuff though, so I don't know, how easily a
systemd conversion is possible. As an intermediate step, you can at
least help systemd along a little, and tell it, that the sysv init scrip
starts a long running process. For that, the magic # pidfile comment
exists. If that is set, systemd will set the proper type (Type=forking)
and will correctly set the main pid, i.e. it will notice if the main
process this.
So, while I would appreciate if exim4 would provide native systemd
support (and if you any questions trying to that, please contact the
[email protected] m-l), we can a least improve the
status-quo by adding
--- exim4.dpkg-dist 2016-09-25 14:46:29.000000000 +0200
+++ exim4 2015-11-16 14:25:07.000000000 +0100
@@ -18,6 +18,7 @@
# Short-Description: exim Mail Transport Agent
# Description: exim is a Mail Transport agent
### END INIT INFO
+# pidfile: /var/run/exim4/exim.pid
Thansk 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.8.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 exim4 depends on:
ii debconf [debconf-2.0] 1.5.59
ii exim4-base 4.88~RC4-2
ii exim4-daemon-light 4.88~RC4-2
exim4 recommends no packages.
exim4 suggests no packages.
-- debconf information excluded
--- End Message ---
--- Begin Message ---
Version: 4.96-20
On 2016-11-13 Michael Biebl <[email protected]> wrote:
> Package: exim4
> Version: 4.88~RC4-2
> Severity: normal
> Hi,
> having a native systemd service for exim4 would be great. The sysv init
> script does a *lot* of stuff though, so I don't know, how easily a
> systemd conversion is possible. As an intermediate step, you can at
> least help systemd along a little, and tell it, that the sysv init scrip
> starts a long running process. For that, the magic # pidfile comment
> exists. If that is set, systemd will set the proper type (Type=forking)
> and will correctly set the main pid, i.e. it will notice if the main
> process this
[...]
Closing, since we have managed to ship a systemd file.
--- End Message ---
