4.74.9-1 strangeness/bugs

[Julian Field]

On 18/12/08 11:34, Jeff A. Earickson wrote:
> On Thu, 18 Dec 2008, Julian Field wrote:
>
>>>>> 3) BUG:  The permissions on /tmp got changed from 1777 to 700 on me
>>>>> during my debug run of 4.74.9-1.  Ouch!
>>>> Fixed.
>>>
>>> Errr, not true.  The other bugs above went away but this one remained
>>> with MailScanner-4.74.10-1.  I checked the status of /tmp (owner and
>>> group = root, chmod 1777) before running a debug version of 4.74.10-1.
>>> Bang!  It chmoded /tmp to 700 right away, so I changed the 
>>> permissions by hand while the debug version was still churning.  The 
>>> test otherwise finished normally.  I repeated the whole process 
>>> again to make sure I was
>>> not dreaming.  Same result.
>> Okay, I'll take another look at that one.
>>>
>>> Question:  Does /var/spool/MailScanner/incoming/Locks and locks get
>> There should just be Locks and not locks as well. Where is "locks" 
>> getting created?
>>> a lot of traffic, or just occasional use when anti-virus profiles are
>>> updated?  In previous versions, all of this lived in /tmp which is
>>> ramdisk in Solaris -- fast.  Will the change to "Lockfile Dir" slow
>>> us down?
>> That's why I put it in /var/spool/MailScanner/incoming as that should 
>> also be on tmpfs in any decently-configured system.
>
> The only thing /var/spool/MailScanner/incoming had on my system before
> playing with the beta version was SpamAssassin.cache.db.  Both a "Locks"
> and a "locks" dir appeared there after starting the beta versions,
The .10 version should only have created a Locks and not a locks dirs 
there. Please check with .11 after removing Locks and locks.
> and
> both dirs contain [av]Busy.lock files.  In my case (Solaris) this 
> directory has always resided on real disk.  /tmp and /var/run are the 
> only tmpfs filesystems in out-of-the-box Solaris 10.  So maybe I 
> should be using a /var/run/MailScanner directory for Lockfile Dir?
No, it's mentioned in plenty of the docs that 
/var/spool/MailScanner/incoming can be on tmpfs.
>   Any other settings
> that should be scribbling to /var/run?
No, you should be mounting /var/spool/MailScanner/incoming on tmpfs and 
using the default paths.
>   Maybe comments should be added
> to the MailScanner.conf file for settings saying "this file can reside
> in tmpfs, not needed across reboots" or "this file is needed across
> reboots, store on physical disk"?
This is already mentioned in the "Incoming Work Dir" setting, which is 
the only place it is relevant. RTFM :-)

Jules

-- 
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

MailScanner customisation, or any advanced system administration help?
Contact me at Jules at Jules.FM

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
PGP public key: http://www.jules.fm/julesfm.asc


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.