$OPTIONS variable missing in "ExecStartPre" of proftpd-core systemd unit

Bug #2059835 reported by kodu.cloud
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
proftpd-dfsg (Ubuntu)
New
Undecided
Unassigned

Bug Description

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]
Type=forking
Environment=OPTIONS= CONFIG_FILE=/etc/proftpd/proftpd.conf
EnvironmentFile=-/etc/default/proftpd
ExecStartPre=/usr/sbin/proftpd --configtest -c $CONFIG_FILE
ExecStart=/usr/sbin/proftpd -c $CONFIG_FILE $OPTIONS
ExecReload=/bin/kill -HUP $MAINPID
PIDFile=/run/proftpd.pid

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.

Best regards,
kodu.cloud team.

kodu.cloud (koducloud)
description: updated
kodu.cloud (koducloud)
summary: - $OPTIONS variable missing in "ExecStartPre" of proftpd-basic systemd
- unit
+ $OPTIONS variable missing in "ExecStartPre" of proftpd-core systemd unit
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.