I think i've found the problem. The umask configuration is taken into
account when the pidfile is created. That's a little bit strange because
i think this setting should only taken into account when files are
uploaded at runtime. Nevertheless, it seems to be a configuration
problem, thus you can c
Hi Hilmar,
the issue exits for a long time. I have many reports about this issue in
the openmediavault forum. To workaround this issue i added a systemd
drop-in to change the file mode before the 'stop' action is executed.
See
https://github.com/openmediavault/openmediavault/commit/439d11d9ad37510
Am 09.05.2020 um 15:29 teilte votdev mit:
Hi Volker,
> The proftpd daemon writes the pidfile with mode 0666 instead of 0644.
> Because of that it is
> not possible to stop or restart the daemon with "systemctl stop proftpd" or
> "systemctl restart proftpd". The reason is the new security check of
Package: proftpd-basic
Version: 1.3.6-4+deb10u5
Severity: important
The proftpd daemon writes the pidfile with mode 0666 instead of 0644.
Because of that it is
not possible to stop or restart the daemon with "systemctl stop proftpd" or
"systemctl restart proftpd". The reason is the new security ch
4 matches
Mail list logo
