JSutils for Computer Energy Saving and Energy Use Calculation
Bookmark and Share
Updated: 06-Oct-2009
JSutils Compact Disk

LANOff Log Files

Latest Version: 4.3
Size: 643KB
Released
23-September-2009
LanOff icon
JSutils software logo

Both the Main and Slave programs generate log files 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.

Main Program Log File Format
The log file generated by the main program has the following format:

<data/time>, <status>, <status details>, <counter>, <communications status>

Where:
<data/time> shows current data and time from local computers 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, UnConfig - Main 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.
<communications status >
- In the format 'w, x, y, z' where: w, x, y and z are the status of Remote Computers 1, 2, 3 and 4 (0 - No Connection, 1 - Connection Error, 2 - Connection OK) or 'No Network' if there is no network connection.

The amount of logging is dependent on the Log Level set in the configuration file which has details of the various levels available. If the Log Level is set to Full details of the configuration will also be included.

<counter> & <communication status> are only shown when the log level is set to Full.

Sample main program log file

Slave Program Log File Format
The log file generated by the client program has the following format:

<data/time>, <status>, <status details>, <counter>, <communications status>

Where:
<data/time> shows current data and time from local computers 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).
<communications status >
- either Fail, OK or Error,

A '* in front of <status> indicates the program is in test mode.

The amount of logging is dependent on the Log Level set in the configuration file which has details of the various levels available. If the Log Level is set to Full details of the configuration will also be included.

<counter> & <communication status> are only shown when the log level is set to Full.

Sample slave program log file