Redefining TimeoutIdle or TimeoutNoTransfer in a configuration file inside /etc/proftpd/conf.d/, after they’ve already been defined in /etc/proftpd/proftpd.conf, fails to change those values for the daemon — that is, after restarting the daemon, the values for those parameters remain as those set in /etc/proftpd/proftpd.conf.
At least TimeoutIdle or TimeoutNoTransfer are affected. TimeoutSession and TimeoutLogin, which (in stock 16.04) haven’t been defined in the master configuration file can be set effectively, but setting them first in the master file, then again to different values inside conf.d reveals them to be equally affected.
On the other hand, (at least) ServerName *can* be overridden in the custom configuration file, so the handling of different configuration knobs in this regard seems to be inconsistent.
Steps to reproduce:
1. Create a /etc/proftpd/conf.d/proftpd.conf with the following lines:
2. Restart proftpd
3. Log into the server, wait 11 seconds
What I expect to happen:
To get kicked out of the server.
What happens instead:
I’m allowed to linger on the server, presumably for the 600 seconds defined for TimeoutNoTransfer in /etc/proftpd/proftpd.conf.