Ahoj,
Dňa Mon, 23 Dec 2024 11:37:57 +0100 Kai Bojens via Exim-users
<[email protected]> napísal:
> Am 23.12.24 um 11:17 schrieb Jeremy Harris via Exim-users:
>
> > I'd be tending to blame systemd, also. What has it started doing
> > differently?
>
> Debian 11 worked fine without any problems. The problems started with
> Debian 12 and the backported version. It is obvious that the systemd
> files changed and now the old init script is not used anymore. It
> "feels" like a timeout and systemd finally killing the daemon. But I
> have no facts to support this at the moment.
AFAIK, the debian's 4.98 version switched from init.d startup script
(converted to systemd unit by systemd's generator) to native systemd
unit.
It includes various Protect*= and Private*= options. IMO you can
override that unit file (systemd edit ...) and try to disable them to
find what collides with your settings. From my unit file (as shown by
systemd cat):
[Service]
...
PrivateTmp=true
ProtectSystem=full
PrivateDevices=true
ProtectHostname=true
ProtectClock=true
ProtectKernelTunables=true
ProtectKernelModules=true
ProtectKernelLogs=true
ProtectControlGroups=true
ProtectProc=invisible
RestrictRealtime=true
I would try to start with ProtectSystem and ProtectProc
regards
--
Slavko
https://www.slavino.sk
--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## [email protected]
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
