monitoring workstation or laptop if sometimes is power off or isn't in network

[Anthony Montibello]

IF I understand your question? you are looking for a way to configure
a host so that its services will keep the last OK state when the host
is no longer available.

This would make schedule downtime not an option, because the checks
still run and would return non-OK states


If this host unavailable is always on a predetermined schedule then
you can use the check_period  and notification_period of the service
definition to reflect the downtime (I think this would work)

An alternate approach to this would be to use passive checks with
either a very large freshness_check_interval or with 
check_service_freshness turned off.  there are disadvantages to doing
this due to frechness_check being global settings.
and it may make it difficult to detect when the host is really down.

good luck
TOny



On 5/9/05, Michał Panasiewicz <wolvverine at tarchomin.pl> wrote:
> how monitoring workstation if sometimes is power off or
> isn't in network:
> If workstation is power off not testing this and not generate alarm for
> host?
> and remember last status for services
> 
> --
> Michał Panasiewicz
> jabber: wolvverine [ at ] chrome [ dot ] pl
> e-mail: wolvverine [ at ] tlen [ dot ] pl , wolvverine [ at ] pld-linux [ dot ] org
> Potrzebujesz Informatyka/Administratora (Warszawa) -skontaktuj sie ze mną
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
>