Novell Documentation: Novell OnDemand Services 2 - Modifying the Watchdog Service Configuration Settings

Modifying the Watchdog Service Configuration Settings

You can use the Watchdog service's configuration settings to provide advanced control of the service, including:

The amount of detail that is output to the service's log file.
How often the service, when functioning as a backup for another Watchdog service, checks to see if the primary Watchdog service is alive.
How often the service, when functioning as a primary service, requests load information from other Watchdog services.
How often the service, when functioning as a primary service, waits for load information to be returned from other Watchdog services before timing out.

The configuration settings are stored in the terminal server's Windows registry under the following key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\DeWatch\Config

The following table describes the configuration settings (values).

Value	Type	Default	Description
SettingsRecacheDelaySecs	DWORD	20	Determines how often the Watchdog service rereads these registry settings.
LogFileOutputFilter	DWORD	0	Determines the amount of information that is output to the logfile. The valid settings are: 0 = errors 1 = errors and warnings 2 = all information The logfile, dewatchlog.txt, is located in the c:\winnt\system32\deframe directory.
LogFileConvertUni	DWORD	0	The default setting (0) causes the Watchdog service to generate a Unicode logfile. If you want the Watchdog service to generate an ansi text file, change the setting to 1. 0 = no 1 = yes
LogGetLastError	DWORD	0	The default setting (0) instructs the Watchdog service to output its error code and message only. If you want the Watchdog service to output additional Windows error information, change the setting to 1. 0 = no 1 = yes
AliveCheckDelaySecs	DWORD	30	Determines how often the Watchdog service, when functioning as a backup service, checks to see if the primary Watchdog service is still available.
AliveCheckTimeoutSecs	DWORD	10	Determines how long the Watchdog service, when functioning as a backup service, waits for the primary Watchdog service to respond to its alive check. If the primary service does not respond within the specified amount of time, the backup service switches roles with the primary service.
DSRecacheDelaySecs	DWORD	30	Determines how often the Watchdog services reads eDirectory for updated information. If the Watchdog service is a primary service, it reads eDirectory to refresh the list of applications assigned to it. If the Watchdog service is not a primary service, it reads eDirectory to see whether it has been assigned primary or backup status.
LoadRequestTimeoutSecs	DWORD	10	Determines how long the Watchdog service, when functioning as a primary service, waits for other Watchdog services to return server load information. If a service's response is not received within the specified amount of time, the service's previous load information is used. NOTE: By default, a primary service requests server load information every 4 seconds. You can change this setting in eDirectory (DeFrame server object > Server Load Configuration tab > Load Config page > Load Refresh Rate field).
SocketSendTimeoutMillis	DWORD	100	Determines how long the Watchdog service will retry sending information through a socket before timing out.
PacketProcessTimeoutMillis	DWORD	100	Determines how long the Watchdog service will hold a socket or IPC waiting for incoming data.