Log 3.0

Category / Domain: Administration
Compatibility SCOL Voy@ger V 2.0c and superior
Update: 08/1998

Function

This administration module is used to record the events that take place on a SCOL site. The Scolmaster uses it to perform a check downstream. Users are therefore advised against integrating this module into the client graphic interface since this module contains sensitive commands: : it is possible to record the conversations between the avatars in a C3D3 cell (but not private conversations via the comutron).
A " log " file will be generated in the scol/partition/log directory in the following format: Site name.log - module name.date.
For every day, a file is create (server schedule).
The log can be as well posted on the interface server as on the customer interface.

This Log module is independent from files generated in the scol/log directory by the Scol virtual machine. Consult the scol textbook (worker's manual) for more details on this subject.

Configuration


Figure 1 : Interface of the Log module

Available commands (by typing command in the text entry field (3) below):

Log: interface allowing to see information relative to avatars : copy the command line in the log file.
Private nickname text: send a private text to an avatar. Example: private guest\ 198 Welcome\ in\ this\ world. Followed with the ENTER key on the keyboard.
Service text: service ( popup ) sends a text to all the avatars under of a message shape. Example: Welcome\ in\ this\ world\ service. Followed with the ENTER key on the keyboard.
Who: post the list of present avatars.
Mem: post resources in computer's memory.
Back: give logs posted in memory.
Download: allows to download a file from the server

(1) : Information of the site since the last server's startup.
(2) : Instant log screening.
(3) : Text entry field.

Application

Action Function
module.event à log.register Takes into account the arrival of the user in the LOG module. Start recording.
module.event à log.unregister Does not take into account any more avatar in the interface of the LOG module. Stop recording
module.event à log.start Start the LOG module at the customer (it is not necessary to start the module at the customer to start recording. In other words, if the customer is not authorized to have the log, it is useless to establish this link. Only link module.événement à log .register is necessary.
module.event à log. !changeLogin Takes into account the change of nickname(login)
module.event à log.log Records the module's data in the LOG module file
module.event à log.destroy Destroyes the LOG module at the customer.

Event Function
log.entering à module Action Entering the LOG module generates an action
log.destroyed à module Action Stopping the LOG module generates an action
log.log à module Action Recording the module's data generates an action

Zone Function Interface Assignment
Log.log Post the panel of control of Log Server Yes