1 Manage Caller Log
This (Sysop) command enables you to manage the caller log that PCBoard creates for the current node . You can view, print, search, and delete the caller log.
Subcommands
| D | Delete caller log. | This subcommand will delete the caller log for the current node. You may want to use this subcommand to periodically delete the caller log to prevent it from taking up too much disk space. WARNING: Once deleted, PCBoard cannot recover that caller log. |
| P | Print caller log. | If you use this subcommand, the caller log for the current node will be displayed on the screen and also sent to the printer port that is defined in PCBSetup. |
| S | Search caller log for text. | The more callers your system has the more difficult it will be to find the information you are looking for in the caller log. PCBoard provides search capabilities to allow you to search the log file for any text. You can do both a simple one word or one phrase search or you can do complex Boolean searches using the AND, OR, and NOT operators. For more information on Boolean searching please see Searching For Text in the Sysop's Guide chapter of this manual. |
| If PCBoard finds a match when searching the caller log, the log entry for the entire call will then be displayed. The search text that was found will be highlighted for clarity. | ||
| When PCBoard searches through the callers logs it does not try to match case. If you tell PCBoard to search for Jim Smith then any caller log that contains the text JIM SMITH would be a match. | ||
| V | View caller log. | Using this subcommand you can view the caller log. The display starts with the most current caller. |
Description
The callers log provides you with information about who has called your system, what node they called in on, highlights of what they did online, what date and time they called, etc. When you view the caller log, PCBoard will display the file to you in reverse order beginning with the last caller to the system.
You will also want to periodically search the caller log because that is where any system error messages may be displayed. In addition, when a user attempts to access a command that is not available to them, that information is almost always written to the caller log.
The caller log is simply a condensed history of what has taken place on the BBS. The 1 command enables you to not only view the information stored in the caller log but also to print and/or delete the caller log.
Examples
To view the current node's caller log on your display, type the following at the command prompt:
1 V
You may want to regularly search your caller log for possible system errors. When executed from the command prompt, the following command will search for any caller log entry that contains the word FAIL or the word ERROR.
1 S FAIL > ERROR