|
|||
Part I Network Services Topics Part II Accessing Network File Systems Topics 4. Managing Network File Systems (Overview) 5. Network File System Administration (Tasks) 6. Accessing Network File Systems (Reference) 8. Planning and Enabling SLP (Tasks) 10. Incorporating Legacy Services Part V Serial Networking Topics 15. Solaris PPP 4.0 (Overview) 16. Planning for the PPP Link (Tasks) 17. Setting Up a Dial-up PPP Link (Tasks) 18. Setting Up a Leased-Line PPP Link (Tasks) 19. Setting Up PPP Authentication (Tasks) 20. Setting Up a PPPoE Tunnel (Tasks) 21. Fixing Common PPP Problems (Tasks) 22. Solaris PPP 4.0 (Reference) 23. Migrating From Asynchronous Solaris PPP to Solaris PPP 4.0 (Tasks) 25. Administering UUCP (Tasks) Part VI Working With Remote Systems Topics 27. Working With Remote Systems (Overview) 28. Administering the FTP Server (Tasks) Administering the FTP Server (Task Map) How to Define FTP Server Classes How to Control the Number of Invalid Login Attempts How to Disallow FTP Server Access to Particular Users How to Restrict Access to the Default FTP Server How to Set Up Anonymous FTP Users How to Create the /etc/shells file Controlling Access to Files on the FTP Server How to Control File Access Commands Controlling Uploads and Downloads on the FTP Server How to Control Uploads to the FTP Server How to Control Downloads to the FTP Server How to Enable Limited Virtual Hosting How to Enable Complete Virtual Hosting Starting the FTP Server Automatically How to Start an FTP Server Using SMF How to Start a Standalone FTP Server in the Background How to Start a Standalone FTP Server in the Foreground How to Shut Down the FTP Server How to Check syslogd for FTP Server Messages How to Use greeting text to Verify ftpaccess How to Check the Commands Executed by FTP Users Configuration Help for Busy Sites 29. Accessing Remote Systems (Tasks) Part VII Monitoring Network Services Topics |
Customizing Message FilesYou can configure the FTP server to return messages that are related to specific events to the FTP client. A welcome message might be set to display when a user logs in to the FTP server. Another message could appear when the user makes a directory change. In addition to plain text, message files can contain one or more magic cookies. A magic cookie is composed of a % (percent sign), followed by a single character. When you embed a cookie in message text, information that is associated with the cookie appears on screen at the point the message file is called. For example, message text might contain the cookie %L: Welcome to %L! When the message is displayed, the magic cookie %L is replaced with the name of the server as defined by the hostname statement in the ftpaccess file. For a complete list of supported message cookies, see ftpaccess(4). Note - If the host name is not defined in the ftpaccess file, the default host name for the local machine is used. How to Customize Message Files
The following is an example of a message file that includes magic cookies: Welcome to %L -- local time is %T. You are number %N out of a maximum of %M. All transfers are logged. If your FTP client crashes or hangs shortly after login please try using a dash (-) as the first character of your password. This will turn off the informational messages that may be confusing your FTP client. Please send any comments to %E. How to Create Messages to Be Sent to UsersAfter the user is logged in, system-related or application-related messages are displayed on screen. The ftpaccess file lists the events that trigger associated message statements.
message /etc/ftpd/Welcome login anon guest message .message cwd=* The preceding example states that the file /etc/ftpd/Welcome is displayed at login for users of the class anon or guest. The second line states that the .message file in the current working directory is displayed for all users. Message files are created relative to the chroot directory for guest and anonymous users. How to Configure the README OptionThe first time a directory is visited, README files can be listed. To configure the README option, add the following entries to the ftpaccess file.
readme README* login readme README* cwd=* The previous example states that any files that match README* are listed at login or when a directory is changed. Here is a sample login that is based on the settings that are used in that example. % ftp earth Connected to earth. 220 earth FTP server ready. Name (earth:rimmer): ftp 331 Guest login ok, send your complete e-mail address as password. Password: 230- 230-Welcome to earth -- local time is Thu Jul 15 16:13:24 1999. 230- 230-You are number 1 out of a maximum of 10. 230-All transfers are logged. 230- 230-If your FTP client crashes or hangs shortly after login please try 230-using a dash (-) as the first character of your password. This will 230-turn off the informational messages that may be confusing your FTP 230-client. 230- 230-Please send any comments to ftpadmin@earth. 230- 230 Guest login ok, access restrictions apply. ftp> cd pub 250-Please read the file README 250- it was last modified on Thu Jul 15 16:12:25 1999 - 0 days ago 250 CWD command successful. ftp> get README /tmp/README 200 PORT command successful. 150 Opening ASCII mode data connection for README (0 bytes). 226 ASCII Transfer complete. ftp> quit 221 Goodbye. |
||
|