How to restart FTPD without causing downtime to FTP processes

[dictum9]

I need the ftp daemon to re-read the configuration file /etc/ftpd/security/tls.conf

I am configuring ftp to use SSL to get ftps going

I made changes to tls.conf but ftp  is not reading it, the values it's getting are from the file before changes, so is  restarting FTP the only way to force it to read tls.conf?

The line from /etc/inetd.conf?

And will it cause downtime to the existing ftp sessions, the machine in question is an FTP server.

[Steven Schweda]

> so is restarting FTP the only way to force it to read tls.conf?

   I know nothing, but I'd expect that if ftpd is not always running,
but rather started on demand by (something like) inetd, then every new
FTP connection request would start a new ftpd instance, so there's not
one, continuously running ftpd to restart.

> The line from /etc/inetd.conf?

   My Web search for:
       hp-ux ftps server
found:
     /t5/x/x/td-p/6463966
which suggests that ftpd has a "-z" option which looks relevant.
Perhaps "man ftpd" (or some other documentation) would reveal more
details.  Of course, with my weak psychic powers, I can't see what's in
your /etc/inetd.conf file.

> And will it cause downtime to the existing ftp sessions, the machine
> in question is an FTP server.

   If each ftpd instance is independently started by inetd, then I'd
expect that changing exactly what gets started for a new session would
have no effect on an existing session.

[pooderbill]

Have you already followed these instructions?

http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c03017718
http://h20565.www2.hpe.com/hpsc/doc/public/display?sp4ts.oid=459574&docId=emr_na-c02137890&docLocale=en_US

ftpd is a daemon that is run by inetd as needed. The ftpd config files are only read when the daemon is started. Any currently running ftpd processes are unaffected. If you have added all the required -z options to /etc/inetd.conf, you'll need to signal inetd (inetd -c) to reread the conf file. NOTE: if you make an error on the ftpd entry in inetd.conf, ftpd (or inetd) will generate error messages in syslog.log and probably not start any new ftpd sessions. Current sessions will finish normally. I would keep the original ftpd line in the inetd.conf as a comment so you can quickly change back and run inetd -c to reread the config file.