Package: tiger
Version: 1:3.2.2-6
Severity: normal
Tags: patch

the following error is reported when:
1. executing /usr/lib/tiger/systems/Linux/2/gen_mounts under dash (as /bin/sh)
2. with the cgroup (or any unrecognized) filesystem mounted
3. and not listed in Tiger_FSScan_(|Non)Local

[: 253: Y: unexpected operator

it's a simple bashism that probably gets rarely triggered due to gen_mounts 
accounting for almost every conceivable filesystem type.

this might be fixed in newer versions, but this is the newest version in 
lenny/stable, and i believe should be tagged as such (but reportbug would allow 
a tag of "lenny" or "stable", though i thought it did previously).

i would normally tag this as minor except that every time gen_mounts gets 
indirectly executed from cron it generates the above error message on stderr 
which generates an email to me.  multiply this times the number of machines it 
happens on and you see how this is no longer minor flooding my inbox.

in creating a patch i realized that setting Tiger_FSScan_NonLocal to "cgroups" 
works around the problem (which i did anyways as gen_mounts doesn't 
categorize), but doesn't solve it.

corey
--- /etc/tiger/tigerrc.orig     2008-09-08 21:21:51.000000000 -0500
+++ /etc/tiger/tigerrc  2009-08-26 10:14:22.000000000 -0500
@@ -292,7 +292,7 @@ Tiger_Crack_Local=Y
 #
 # Who gets output from 'tigercron'?
 #
-Tiger_Mail_RCPT=root
+Tiger_Mail_RCPT="root"
 #
 # List of '/' separated filename globs (NOT pathnames) to look for
 # on the filesystems.
@@ -311,7 +311,7 @@ Tiger_FSScan_Unowned=Y              # files with und
 #  The following variables change the way the GET_MOUNTS (gen_mounts) script 
works:
 Tiger_FSScan_WarnUnknown=Y     # Warn about unknown filesystems used
 Tiger_FSScan_Local=''          # Filesystems considered to be local to the 
system, pipe-separated
-Tiger_FSScan_NonLocal=''       # Filesystems considered to be non-local to the 
system, pipe-separated
+Tiger_FSScan_NonLocal='cgroup' # Filesystems considered to be non-local to the 
system, pipe-separated
 #
 # Should we scan read-only filesystems
 #

Reply via email to