The FTP server can be started in one of two ways:
As a standalone server that is started from the command line or by a startup script
You can add a nowait entry in inetd.conf file to start the FTP server. If the site handles many connections, the FTP daemon can also be run in standalone mode. For more information, see inetd.conf(4). See also in.ftpd(1M) for information on additional command-line options.
Become superuser.
Add a nowait entry to the inetd.conf file:
ftp stream tcp6 nowait root /usr/sbin/in.ftpd in.ftpd -a |
The -a option is specified to enable the use of the ftpaccess file.
Signal inetd to reread the inetd.conf file.
# pkill -HUP inetd |
The FTP server can also be run independently of the inetd.conf as a standalone server.
A standalone server always has the quickest possible response time, and is intended for large servers that are dedicated to providing FTP service. The standalone server provides low connection latency for dedicated servers because the standalone system never has to be restarted. The standalone server is always running—even during off-peak hours—waiting indefinitely for connections.
Become superuser.
Add a # sign at the start of the ftp service line in the inetd.conf file to comment out the entry.
Signal inetd to reread the inetd.conf file.
# pkill -HUP inetd |
Start the standalone FTP server.
# /usr/sbin/in.ftpd -a -S |
Add the line to an FTP server startup script. See “Run Control Scripts” in System Administration Guide, Volume 1 for information on creating a system startup script.