4.74.9-1 strangeness/bugs

[Julian Field]

On 17/12/08 22:08, Jeff A. Earickson wrote:
> On Wed, 17 Dec 2008, Julian Field wrote:
>
>> On 17/12/08 14:57, Jeff A. Earickson wrote:
>>> Julian,
>>>
>>> I attempted to go with 4.74.9-1 this morning, and got bit.
>>> Here is my list of issues:
>>>
>>> 1) I noticed that "Lockfile Dir" is now 
>>> /var/spool/MailScanner/incoming/Locks instead of /tmp.
>>> This directory didn't exist, but I notice that starting up
>>> MailScanner created both this directory and a "locks" directory
>>> there, and populated it with [antivirus]Busy.lock files.
>> Correct.
>>>
>>> At startup, I got the complaint:
>>>
>>> -n Starting MailScanner...
>>> sh: /usr/sbin/mailscanner_create_locks: not found
>> Fixed.
>>> Error: Attempt to create locks in 
>>> /var/spool/MailScanner/incoming/Locks failed!
>> Caused by the previous error.
>>>
>>> These complaints are new.
>>>
>>> 2) I ran the update_virus_scanner, and got:
>>>
>>> # /opt/MailScanner/bin/update_virus_scanners
>>> Can't open /etc/MailScanner/MailScanner.conf: No such file or 
>>> directory.
>>> Can't open /etc/MailScanner/MailScanner.conf: No such file or 
>>> directory.
>>> Can't open /etc/MailScanner/MailScanner.conf: No such file or 
>>> directory.
>>>
>>> My MailScanner.conf lives in /opt/MailScanner/etc/MailScanner.conf, not
>>> /etc/MailScanner.  /etc/MailScanner only contains my customized 
>>> rules/reports
>>> files.  Hmmm.  I could create a symlink there but don't want to.
>> Fixed.
>>>
>>> 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.

Jules

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

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654


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