VSFTPD - Standalone vs. inetd/xinetd

Hi,
In attempting to configure the VSFTPD how do I determine in which mode it is running? In other words, I want do identify whether the Daemon is running in standalone mode or under inetd so I can set the configuration file values properly.
Also, would someone please elaborate on the advantages or disadvantages of using one mode over the other?
Thanks,
Dov

Running under xinetd allows you run one process less because xinetd is shared among various other small services, at the cost of slightly slower startup because vsftpd has to be run on demand. This is fine if you only use ftp occasionally. If ftp is a heavily used service then running vsftpd standalone is better.

doxenberg wrote:
> Hi,
> In attempting to configure the VSFTPD how do I determine in which mode
> it is running? In other words, I want do identify whether the Daemon is
> running in standalone mode or under inetd so I can set the configuration
> file values properly.

The configuration file holds the key to this choice.
If it says:
listen=YES
then vsftpd is in daemon mode. Of course there must not be a xinetd file
in which vsftpd is also enabled.

> Also, would someone please elaborate on the advantages or disadvantages
> of using one mode over the other?

Daemon mode uses marginally more resources, but is faster with higher
connect loads. Also it lets you start and stop the FTP server without disrupting
other services.

I think xinetd has this sorted out. If you send xinetd the appropriate signal it doesn’t touch services whose configuration hasn’t changed. But you have to do rcxinetd reload, not rcxinetd restart.