Hi all:

We were having a weird problem with nmblookup firing for a host that
was disabled with:

  $Conf{BackupsDisable} = '2';

using BackupPC 3.1.0. The same thing happend when set to 1. My claim
is that BackupPC shouldn't be attempting to resolve any host with
BackupsDisabled set to 2, and it should not be looked up when it is
set to 1, unless a user explicitly requests that the host be backed
up. (I.E. it shouldn't be queued just because it's in the hosts file.)

The host was removed from DNS, so the fallback to nmblookup was
'expected' I guess, but not valid.

My workaround was to disable all nmblookups using:

  $Conf{NmbLookupPath} = '/bin/true';
         
in the main config.pl file since we don't have any windows boxes in
range of the backup servers. YMMV.

-- 
                                -- rouilj

John Rouillard
System Administrator
Renesys Corporation
603-244-9084 (cell)
603-643-9300 x 111

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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/