Novell OPEN ENTERPRISE SERVER - CONVERSION GUIDE 12-2010, Implementation Manual

Page: 197 / 296

File Services 197
17.5.2 Administering and Managing Pure-FTPd on an OES 2
Server

“Starting Pure-FTPd” on page 197

“Initializing Multiple Instances” on page 197

“Unloading Specific Instances” on page 198

“Pure-FTPd Remote Access Implementation” on page 198
Starting Pure-FTPd
Start the Pure-FTPd server using the
rcpure-ftpd
command.
Initializing Multiple Instances
Pure-FTPd is loaded by using a configuration file. Multiple instances of Pure-FTPd can be loaded
using different configuration files.
By default, an instance of Pure-FTPd using
/etc/pure-ftpd/pure-ftpd.conf
file is loaded at
the boot time by init.d script. For loading multiple instances, new configuration files need to be
created.
To load a new instance of Pure-FTPd:
1 Create a new configuration file for each instance.
For example: Copy
/etc/pure-ftpd/pure-ftpd.conf
to a different location. Rename the
file to
pure-ftpd1.conf
and move it to
/etc/opt/novell/pure-ftpd1.conf
.
2
Modify the following settings in the configuration file to avoid IP address or port conflicts
between the instances:

PIDFile: Points to the full path of the PID file created by the pure-ftpd instance. PID file
is used for unloading a particular instance of pure-ftpd. Hence, ensure that the PID File
path is unique for every instance.
For example:
/var/run/pure-ftp1.pid
,
/var/run/pure-ftp2.pid
.

Bind: By default, pure-ftpd binds to all the IP addresses on the system and listens to
requests over port 21. Modify the settings of the bind such that all the pure-ftpd instances
bind to different IP addresses or port combinations.
edir_ldap_port 389 LDAP port of the eDirectory server
AnonymousOnly no Enables authenticated connection to pure-ftp server
NoAnonymous yes Disables anonymous connection
ChrootEveryone no Allows the user to browse outside the home directory.
This configuration is required for remote server navigation
Parameter Description