This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong. ===== 13 View Node Caller Log ===== Enables you to view other node's caller logs from any other node. You may search or view any or all node's caller logs. ==== Subcommands ==== |**[node #]**|Node number.|The node number you wish to view or A to view all nodes. If you enter a node number that does not have a caller log then an error message will be written to the caller log notifying you that the caller log for the node specified does not exist. In addition, entering a number which exceeds the number of nodes in your software license will re-display a list of who is currently online so that you can pick a valid node.| |**A**|All caller logs.|Specifies that all node log files should be used not just an individual node. This subcommand is most useful when used in a search using the S subcommand.| |**S**|Search for text.|The more callers your system has the more difficult it will be to find the information you are looking for in the various caller logs. PCBoard provides capabilities for you to search the log file for any text. You can do a simple one word, one phrase, or a complex Boolean search 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 caller 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. ==== Description ==== The caller logs provide 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 want to periodically search the caller log because that is where any system error messages are recorded. In addition, when a user attempts to access a command that is not available to them, that information is written to the caller log. ==== Examples ==== To view node 5's caller log you would type the following at the command prompt: 13 5 You may want to regularly search all of your caller logs for possible system errors. When executed from the command prompt, the following command will search for any caller log entry on any node that contains the word FAIL or the word ERROR. 13 A S FAIL > ERROR