Ticket #370 (closed defect: fixed)

Opened 22 months ago

Last modified 22 months ago

CheckProcState: Documentation and functionality ambiguous with respect to sensing excess but not absence of process

Reported by: auadfh Owned by: mickem
Priority: 1 Milestone: 0.3.8
Component: CheckSystem Version: 0.3.7
Severity: Bugs Keywords:
Cc:

Description

In CheckProcState it says that process=state where process is the name of the executable and state is either started or stopped.

In the example down the bottom, however, it says:

CheckProcState MaxWarnCount=4 MaxCritCount=10 ShowAll notepad.exe=running

I've been trying to monitor for only an excess of processes using "started" as the state. The process not running is ok.

So either:

  • running is wrong..
  • it's a synonym for started
  • it's like started but allows for the process to not actually be running by default unless limit set?

Either way, clarification in doco would be useful.

Change History

comment:1 Changed 22 months ago by mickem

  • Status changed from new to closed
  • Resolution set to fixed
  • Milestone set to 0.3.8

Sorry.

It should be started.

Fixed.

Michael Medin

Note: See TracTickets for help on using tickets.