|
 |
AllOff
Log File |
Latest
Version: 3.2
Size: 506KB
Released
14-August-2009 |
 |
|
|
 |
The program generates a log file to enable fault finding and monitoring to be carried out. The amount of logging is dependent on the Log Level set in the Configuration Screen which has details of the various levels available. If the Log Level is set to Normal or Full the program version will be included on start up. If the log level is set to Full details of the configuration file will also be written to the log on start up. Setting the log level to Full will generate very large log files and is only useful for debugging. If the log file is deleted a new one will be created the next time the program is started. The log file can normally be found in the log directory of the main program (usually c:\program files\JSutils\AllOff\Log).
By clicking on the Archive button the log file can be saved and a new one created. Archived results log files are stored in the same directory as the log file using the file naming convention AllOff_<year><month><day>_z.log where z is a number starting at 1 allowing multiple files to be archived on a single day.
Main Program Log File Format
The log file generated by the main program has the following
format:
<data/time>, <status>,
<status details>, <counter>, <cpu load>, <average
cpu load>, <keyboard, mouse and connection status>
Where:
<data/time> shows current data and time
from the computer's internal clock.
<status> shows program status (Close
- program ended normally, Config - configuration change, Enter - program enters new mode,
Exit - program terminated by exit button, Hibernate - program in hibernate delay, Inactive - program
inactive, Monitor - program in monitor off delay, Power Off
- program in power off delay, Reboot - program in reboot delay,
Reset - program reset by reset button, Run - program active
and running, Simulate - program simulating action, Shutdown
- program in shutdown delay, Standby - program in standby delay, Start - program starts)
<status details> shows status details(Activate,
Initialise, Hibernate, Monitor, Power Off, Reboot, Run, Shutdown, Standby, Test, Updated).
<count> is the value of the internal
program counter (count will be negative if the program is started after the fixed activation time).
<cpu load> - instantaneous cpu load(%),
<average cpu load> - average cpu load
over the period specified.
<keyboard, mouse & connection status> - 'K' indicates key press, 'M' indicates mouse movement in previous second, 'S' indicates connected to slave (an 'E' indicates connection error)
A '*' in front of <status> indicates
the program is in test mode.
<cpu load>, <average cpu load> and <keyboard, mouse and connection status> are
only shown if the log level is set to Full.
Sample main program log file
Slave Program Log File Format
The log file generated by the slave program has the following
format:
<data/time>, <status>,
<status details>, <counter>, <communications status>
Where:
<data/time> shows current data and time
from the computer's internal clock.
<status> shows program status (Close
- program ended normally, Config - configuration change, Enter - program enters new mode,
Exit - program terminated by exit button, Inactive - program
inactive, Monitor - program in monitor off delay, Power Off
- program in power off delay, Reboot - program in reboot delay,
Reset - program reset by reset button, Restart - when restarting
hibernate or standby, Run - program active
and running, Simulate - program simulating action, Shutdown
- program in shutdown delay, Standby - program in standby delay,
Start - program starts, UnConfig - Slave program not configured).
<status details> shows status details(Activate, Initialise, Hibernate, Monitor, Power Off, Reboot, Run, Shutdown, Standby, Test, Updated, ******** - program not configured).
<count> is the value of the internal program
counter (count will be negative if the program is started after the fixed activation time).
<communications status > - show the status of communications with the main program (Fail, OK or Error)
A '*' in front of <status> indicates
the program is in test mode.
<communications status> is
only shown if the log level is set to Full.
|
