Usage
Previous Topic  Next Topic 

daeMON is straightforward to use. At an elevated command prompt, enter:


daemon.exe [Option] [Option] ...


Where Option is one or more of the following in combination:


Option

Description

-a

Monitor all FireDaemon Pro services. Saves having to specify multiple -s. Disabled services are ignored. Services are enumerated alphabetically by service shortname.

-c n

Kill subprocess if process consumes more than n% CPU per core over the monitoring frequency. If your app is multithreaded across multiple cores make n > 100.

-d

Dynamic service monitoring. Service list will be re-populated each monitoring cycle allowing for the dynamic inclusion/exclusion of services in the monitoring group. Useful in conjunction with -a.

-e shortname

Service to ignore. Service short name must be supplied. Multiple -e can be supplied. Useful in conjunction with -a.

-f n

Monitoring frequency in n-seconds. If not specified default is 30 seconds.

-g

Don't restart all services when monitoring in group mode. Only restart from the first failed service. So if three services are monitored: A, B and C and if B fails then only B and C will be restarted.

-h

Command line help.

-i n

Ignore high CPU and memory across n x monitoring intervals. CPU and memory has to be greater than their respective limits for each monitoring interval before it is killed. This option has no effect without -c or -m.

-j

Just stop all monitored services if one fails. Don't bother restarting anything.

-k

During service enumeration (-a or -s) ignore services that are manual start and are stopped.

-l server=user:[email protected]

User credentials for connecting to a remote machine. Multiple -l can be supplied. This option is not required to connect to a remote machine - only if specific authentication credentials are required

-m n

Kill subprocess if process consumes more than n x MB of RAM over the monitoring frequency.

-o

Run once. Don't continually monitor. Useful when wanting to just take a service snapshot.

-p

Passive monitoring. If a service is down or a subprocess has crashed - don't bother restarting the service group.

-q

Quiet mode. Don't bother logging anything.

-r

Restart the individual services not the group. Works in conjunction with -j except that the individual service is not started again.

-s shortname

Service to monitor. Service short name must be supplied. Multiple -s can be supplied. Overriden by -a. Disabled services are ignored. This can be the shortname of a built-in Windows service or a FireDaemon Pro service. Services specified using -s are monitored in the same order as specified on the command line and always supersede services enumerated via -a. Remote services can be specified as: \\server\service See -l for specifying credentials when connecting to a remote machine.

-v

Verbose mode. Dump running state of service as well as process ID (PID) of subprocess.