On 01/26/10 05:31, Personal Técnico wrote:
> Hi,
>
> I have modified my check-client script as following:
>
> #! /bin/bash
> jobClient=$1
> if ( echo "sta client=${jobClient}" | bconsole | grep -v -q "Failed to
> connect to Client" ); then
> exit 0
> else
> exit 1
> fi
>
>
> With this script, if client is on, backup runs with no problem, but if
> client is off, bacula-dir is trying to connect during 15 minutes... What
> I want to avoid is this: waiting 15 minutes. If job has a "Run Before
> Job" parameter and it returns "1" (client is off), I thought job was
> cancelled inmediatly it started:
>
> 1. first it was scheduled at time X:Y
> 2. after scheduling, it was started at X:(Y+any minutes) (depending
> previous scheduled jobs)
> 3. but if client is not accessible, job is cancelled at X:(Y+any
> minutes + some seconds).
You might try the attached checkhost script instead. It first checks
whether the host is actually alive and on the network, then whether it's
listening on port 9102, instead of going straight to trying to connect
to it from the console. Trying to use the console for this purpose is,
as you've discovered, very slow.
--
Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355
alaric AT caerllewys DOT net alaric AT metrocast DOT net phil AT
co.ordinate DOT org
Renaissance Man, Unix ronin, Perl hacker, Free Stater
It's not the years, it's the mileage.
checkhost
Description: Text document
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com _______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
