John writes:
> 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.)
It still gets queued because there might be backups that need to expire.
You are right - the disable check happens after the host alive check.
It was done that way to handle the dhcp = 1 case (where you don't know
which host it is until you run nmblookup).
But in the normal case that check should be done earlier. I'll add
that to the todo list.
Craig
-------------------------------------------------------------------------
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@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
