Search

LOG LOGS

[:: Legends Of The Jedi ::]
Logging your connection is prudent, if you intend to protect yourselves. If you
are permed unfairly you must produce a log to fight the `unfair` death when
requesting a restore with the RPC. It is also imparative that the permer
maintains logs of PK incidents in the event that the permed person requests a
restore. This file deals solely with how to log. For information on the restore
process, refer to help restore.

Most clients you use have their own logging ability, and that will be accessed
through their own help files. It is wise to establish what that specific client
uses as logging procedure, and perform a test. Most people who use telnet make
the false assumption that it lacks a logging function.

To log in Microsoft Telnet:

Start the telnet program. Type 'set logfile log.txt' where log.txt is any name
you'd like to use. Be aware that it will not APPEND to the logfile, it will
replace it each time.

To log in Gmud:

Click on FILE, and then LOGGING from the drop-down list. Specify your filename.

To log in Portal GT:

Click on SCROLLBACK, then select 'Log incoming text...', and specify your log
file.

To log in Zmud:

Option 1) CRTL + L or click on file, then log from the drop down list and enter
a file name to save the log under.
Option 2) Click File, select 'Save buffer' and enter a file name to save the
log as. Caution: This method is only as effective as the size of your scroll
back buffer.

To log in MUSHCLIENT:

Click File -> Log Session. Edit the options as necessary then click 'OK'.
Alternatively, the keystroke Shift+Ctrl+J opens the same dialogue.

&To log in TinTin++:

&#LOG {APPEND|OVERWRITE|OFF} {<FILENAME>}
&Example: #LOG {APPEND} {/home/Frump/.tintin/lotj.log}

See Also: Help Perm, Help Restore, Help RPC