Tiger, dirvish and dangling symlinks

[Dale Amon]

I am working on a backup box with a huge disk capacity
that is being used as a dirvish incremental backup for
a bunch of systems.

This of course means there are just thousands upon
thousands of 'apparently' danglying symlinks since
the backups are 'out of context' as it were.

This causes tiger to output useless emails about
them and waste space in security logs about them.

So is there a way to simply tell tiger to not look
at certain disk drives? It seems rather silly to have
it wasting time processing 30-40TB of backups when all
that is needed is to monitor the actual system disks.

Ad Astra,
Dale Amon

[Javier Fernández-Sanguino Peña]

On Tue, Sep 01, 2009 at 08:53:34PM +0100, Dale Amon wrote:
> So is there a way to simply tell tiger to not look
> at certain disk drives? It seems rather silly to have
> it wasting time processing 30-40TB of backups when all
> that is needed is to monitor the actual system disks.

IIRC You can use the Tiger_FSScan_NonLocal variable to have Tiger skip those
filesystems that are not considered "local" or you can disable (in
/etc/tiger/cronrc) the checks that will process the filesystem starting from
/ (check_perms, find_files, check_devices

Regards

Javier

[Dale Amon]

On Mon, Sep 28, 2009 at 01:12:31AM +0200, Javier Fernández-Sanguino Peña wrote:

> On Tue, Sep 01, 2009 at 08:53:34PM +0100, Dale Amon wrote:
> > So is there a way to simply tell tiger to not look
> > at certain disk drives? It seems rather silly to have
> > it wasting time processing 30-40TB of backups when all
> > that is needed is to monitor the actual system disks.
>
> IIRC You can use the Tiger_FSScan_NonLocal variable to have Tiger skip those
> filesystems that are not considered "local" or you can disable (in
> /etc/tiger/cronrc) the checks that will process the filesystem starting from
> / (check_perms, find_files, check_devices
>
> Regards
>
> Javier

Thanks. I'll look into that!