Yup, got it; thank you; problem solved.

However, my solution was to set $conf{PingCmd} in the host config to
"/bin/echo" because $conf{PingPath} looks to me to be a global only and
I would like to keep pings for local machines.  But this does solve the
ping problem so far.  Thank you for the solution.

Any thoughts if this is considered normal or should his indicate some
area of the system that's buggy?  I ask only because as I found, the
commands succeed on the command line but fail from the GUI and the using
"/bin/echo" strikes me more as 'work around' than actual explanation for
the behavior.  I am happy to do more testing if that's the case if more
knowledgeable folk can suggest any helpful directions.

Thanks again,
Eric


On Thu, 2011-11-03 at 20:33 -0500, Les Mikesell wrote:
> On Thu, Nov 3, 2011 at 7:54 PM, Eric Chowanski <eric AT wwek DOT org> wrote:
> > If you mean the time out I've changed it to 10000, which AFAIK means ten
> > seconds.  And as you'll see below, I see results on the command line in
> > about 1 second, so an order of magnitude larger should get the job done
> > if that's the issue.  But perhaps that's not what you meant.
> 
> No, see $conf{PingPath} in the docs.  If you use something that always
> succeeds like /bin/echo, it won't matter if a ping works or not.
> 



------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/