Logging connections (and attempted connections) to your FTP server is important for several reasons. First, you can determine what files are being accessed on your server the most, as well as when and by whom. Knowing user habits can help you plan to provide better services. Also, by examining the contents of your log files you can identify abuse of your system, such as illegal access attempts, improper deletion of files, and files that shouldn't be uploaded to your FTP server. To begin configuring your logging options, choose the Logging tab, shown in Figure 6.

Figure 6: The Logging configuration tab.

The logging tab allows you to set the log file and turn logging on and off. By default all four of the following logs are created and saved in the Rumpus Folder inside your server's Preferences folder. You may change the name or location of any of these files by clicking on the appropriate "Log File" button. If you choose the same folder and filename for two (or all four) of the logs, then the logging information for each log type will be stored in the same log file.

Keep Anonymous Access Log

When checked, a log file is maintained that records information on each anonymous user's IP address, the time and date of the connection, and the commands issued by the user's FTP client, along with the result of each command.

Keep Secure Access Log File

When checked, a log file is maintained that records the same information as for anonymous users. Note that passwords are not recorded for registered users.

Keep Anonymous Password Log

When checked, a file is created for storing the passwords entered by anonymous users. People generally enter their e-mail address as their anonymous FTP password, so this log can be useful for the Rumpus administrator for debugging and statistics.

Failed Access Log

Rumpus can maintain a log detailing any failed login attempt. This log can be used to warn you about unauthorized users attempting to hack into your FTP server. It will also warn you about server problems or potential errors. For example, the log will show you if users are being rejected due to the maximum number of simultaneous users.