[ProFTPD-committers] [Bug 3553] Ability to stop/start proftpd without killing existing connections

[b***@horde.net]

http://bugs.proftpd.org/show_bug.cgi?id=3553


TJ Saunders <***@castaglia.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@impulsed.net,
| |***@secure-computing.net

[b***@horde.net]

http://bugs.proftpd.org/show_bug.cgi?id=3553





--- Comment #1 from Thomas L. Shinnick <***@io.com> 2010-12-10 17:31:01 ---
So this would allow replacement of the proftpd executable, without impacting
currently running sessions, as opposed to, or rather similar to, the ability to
use SIGHUP to replace the active _configuration_ ?

The enhancement would simply extend the existing flexibility of changing out
the configuration dynamically, to changing out the executable file when running
ProFTPD in daemon mode?

(And this does not affect or enhance use of xinetd initiated ProFTPD sessions?)

Sounds good to me (though I run using xinetd...)

[b***@horde.net]

http://bugs.proftpd.org/show_bug.cgi?id=3553





--- Comment #2 from TJ Saunders <***@castaglia.org> 2010-12-10 17:35:39 ---
Exactly -- this functionality would allow for changing the binary being
executed without affecting currently running sessions. It would only work for
proftpd daemons running in standalone mode; no impact for proftpd daemons
running with "ServerType inetd" in their config.

[b***@horde.net]

http://bugs.proftpd.org/show_bug.cgi?id=3553
"Would it make sense not to exit parent process but instead stop
listening to network connections, rename pid file etc and automatically
start new proftpd executable?"

[b***@horde.net]

http://bugs.proftpd.org/show_bug.cgi?id=3553

--- Comment #4 from TJ Saunders <***@castaglia.org> 2011-05-19 14:41:25 EDT ---
See, for example, the nginx docs for this sort of functionality:

http://wiki.nginx.org/CommandLine