Some notes towards a VMS specific FTP section

[Stephen Tihor 212 998 3052 <[e-mail]>]

VMS
---

Using MULTINET Anonymous FTP configuration is fully described in the
documentation.   A common configuration is to set up the ANONYMOUS user
as described in the documentation, being careful to include allthe
restrictions to keep it from being used as an normal interactive account.

This username should have a unique UIC member and group numbers.  
They should not be granted a disk quota unless you want to before proper
logging.  In that case the home directory of the ANONYMOUS user should be a
suitable directory protected against other users, preferably on a different
disk from the anonymous ftp area.   

The actual anonymous file area should be defined using the MULTINET CONFIGURE
command and the SET ANONYMOUS-FTP-DIRECTORY option.  This will create an
executive mode system wide logical name MULTINET_ANONYMOUS_FTP_DIRECTORY
when you next reboot which will limit Anonymous FTPs to that directory and its 
subdirectories.

By placing the user ANONYMOUS's home directory outside of the tree which
ANONYMOUS FTP is allowed to access you prevent outside users from removing or
modifying the log files. To keep the directory size down youshould periodically
run a job to collected interesting elements of the files and move or delete
them.

The ANONYMOUS user executes its LOGIN.COM file when it starts up.   This file
should not be owned by anonymous, should only be readabled by ANONYMOUS, and
should be placed in a directory where ANONYMOUS's UIC can not write files.

If you are keeping the log files that LOGIN.COM should define the logical name
MULTINET_FTP_SERVER_LOG_LIMIT to be a reasonable number or "-" to prevent the
command file from purging down the log files and destroying information.

If you choose to configure additional Anonymous like accounts follow the same
general outline and record their usernames in the main anonymous FTP area.
You will need to define the logical names manually for those accounts.