hi,
i've been trying to track down the reason(s) that /var/root/.spamassassin keeps
getting created by 'spamassassin --lint ...'.
it seems that it's related to, and varies with, the SA lock_method defined ...
if, in local.cf:
lock_method nfssafe # this is the default
then, after:
rm -rf /var/root/.spamassassin
spamassassin --lint \
--debug \
--siteconfigpath=/var/Data/SpamAssassin \
--configpath=/var/Settings/SpamAssassin \
--prefs-file=local.cf \
--nocreate-prefs
grep "locker:" on the output -->
[2824] dbg: locker: safe_lock: created
/var/Settings/SpamAssassin/.spamassassin/bayes.lock.devbox.internal.testdomain.com.2824
[2824] dbg: locker: safe_lock: created
/var/Settings/SpamAssassin/.spamassassin/bayes.lock.devbox.internal.testdomain.com.2824
[2824] dbg: locker: safe_lock: created
/var/root/.spamassassin/auto-whitelist.lock.devbox.internal.testdomain.com.2824
[2824] dbg: locker: safe_lock: trying to get lock on
/var/root/.spamassassin/auto-whitelist with 0 retries
[2824] dbg: locker: safe_lock: link to
/var/root/.spamassassin/auto-whitelist.lock: link ok
[2824] dbg: locker: safe_unlock: unlink
/var/root/.spamassassin/auto-whitelist.lock
and,
ls -al /var/root/.spamassassin
total 12
drwx------ 3 root wheel 102 Jun 27 15:57 .
drwxr-x--- 25 root wheel 850 Jun 27 15:56 ..
-rw------- 1 root wheel 12288 Jun 27 15:57 auto-whitelist
whereas if, in local.cf:
lock_method flock
the same
spamassassin --lint ...
results in:
[2838] dbg: locker: safe_lock: created
/var/root/.spamassassin/auto-whitelist.mutex
[2838] dbg: locker: safe_lock: trying to get lock on
/var/root/.spamassassin/auto-whitelist with 30 timeout
[2838] dbg: locker: safe_lock: link to
/var/root/.spamassassin/auto-whitelist.mutex: link ok
[2838] dbg: locker: safe_unlock: unlocked
/var/root/.spamassassin/auto-whitelist.mutex
ls -al /var/root/.spamassassin
total 16
drwx------ 4 root wheel 136 Jun 27 16:02 .
drwxr-x--- 25 root wheel 850 Jun 27 16:01 ..
-rw------- 1 root wheel 12288 Jun 27 16:02 auto-whitelist
-rw------- 1 root wheel 5 Jun 27 16:02
auto-whitelist.mutex
in the first case, locks are created where, i presume, they _should_ be -- in
my defined (siteconfigpath)/.spamassassin, as WELL as in /var/root/...
in the latter case, ONLY in /var/root/...
is this correct behavior? why is anything being created in /var/root? and why
is it different for the two locking methods?
richard
