The $OPTIONS environment variable is defined in the /lib/systemd/system/proftpd.service file and used in the "ExecStart" line when starting the service, but it is not used when calling --configtest in the "ExecStartPre" line:
If the server's hostname cannot be resolved for some reason, proftpd will not start.
Adding the line below to the /etc/default/proftpd file can circumvent this issue:
OPTIONS="-S 0.0.0.0"
However, due to the absence of the $OPTIONS variable in "ExecStartPre", the OPTIONS line in the /etc/default/proftpd will be ignored, --configtest will fail and proftpd will not start.
We believe the $OPTIONS variable should be added to the "ExecStartPre" line.
Package: proftpd-core
Version: 1.3.7c+dfsg-1build1
Architecture: amd64
The $OPTIONS environment variable is defined in the /lib/systemd/ system/ proftpd. service file and used in the "ExecStart" line when starting the service, but it is not used when calling --configtest in the "ExecStartPre" line:
[Service] OPTIONS= CONFIG_ FILE=/etc/ proftpd/ proftpd. conf =-/etc/ default/ proftpd /usr/sbin/ proftpd --configtest -c $CONFIG_FILE /usr/sbin/ proftpd -c $CONFIG_FILE $OPTIONS /bin/kill -HUP $MAINPID /run/proftpd. pid
Type=forking
Environment=
EnvironmentFile
ExecStartPre=
ExecStart=
ExecReload=
PIDFile=
If the server's hostname cannot be resolved for some reason, proftpd will not start. proftpd file can circumvent this issue:
Adding the line below to the /etc/default/
OPTIONS="-S 0.0.0.0"
However, due to the absence of the $OPTIONS variable in "ExecStartPre", the OPTIONS line in the /etc/default/ proftpd will be ignored, --configtest will fail and proftpd will not start.
We believe the $OPTIONS variable should be added to the "ExecStartPre" line.
Best regards,
kodu.cloud team.