General Thankyou (still diagnosing fault)

Dave Filchak submit at zuka.net
Mon Jan 12 21:15:22 GMT 2009


Julian Field wrote:
>
>
> On 12/1/09 19:59, Dave Filchak wrote:
>> Julian Field wrote:
>>>
>>>
>>> On 12/1/09 16:41, Dave Filchak wrote:
>>>> <snip>
>>>>> The cron job will probably put it back. Okay, next let's find if 
>>>>> it is the script run by cron that is causing the problem, or the 
>>>>> environment in which it is run.
>>>>>
>>>>> /usr/sbin/update_virus_scanners
>>>>> ls -al /var/spool/MailScanner/incoming/Locks
>>>>>
>>>>> and show me the output of those two. I want to see if the 
>>>>> update_virus_scanners script successfully finds the uid and gid or 
>>>>> not.
>>>> /usr/sbin/update_virus_scanners
>>>> lduid = , ldgid =
>>>>
>>>> Does not appear to.
>>> Aha, we're getting somewhere.
>>> Now edit /usr/sbin/update_virus_scanners.
>>> At the very top there are 3 lines which set LOCKDIR, RUNASU and RUNASG.
>>> Immediately after them add these 3 lines
>>> echo LOCKDIR = \'$LOCKDIR\'
>>> echo RUNASU = \'$RUNASU\'
>>> echo RUNASG = \'$RUNASG\'
>>>
>>> Then run /usr/sbin/update_virus_scanners as root.
>>>
>>> I am hoping it will print something like this:
>>> LOCKDIR = '/var/spool/MailScanner/incoming/Locks'
>>> RUNASU = 'postfix'
>>> RUNASG = 'postfix'
>>> lduid = 89, ldgid = 89
>>> Let us see what your version prints.
>>>
>>> We should be able to sort this pretty soon, we're getting very close 
>>> to the source of the problem.
>>>
>>> Jules
>>>
>> OK ... this is what I got from the first addition:
>>
>> /usr/sbin/update_virus_scanners
>> LOCKDIR = '/var/spool/MailScanner/incoming/Locks'
>> RUNASU = 'postfix '
>> RUNASG = 'postfix '
>> lduid = , ldgid =
>>
>> Then with the addition of the second part, I get:
>>
>> /usr/sbin/update_virus_scanners
>> LOCKDIR = '/var/spool/MailScanner/incoming/Locks'
>> RUNASU = 'postfix'
>> RUNASG = 'postfix'
>> lduid = 80, ldgid = 80
>>
>> which looks much better ... yes?
> Perfect! At last :-)
>
> Attached are new versions of mailscanner_create_locks and 
> update_virus_scanners for you, which are slight improvements on the 
> versions you now have. Please let me know if these work okay for you 
> and correctly set the ownership of the files in 
> /var/spool/MailScanner/incoming/Locks.
>
> I have gzipped the files to (a) save bandwidth and more importantly 
> (b) stop my email client from attempting to add any signature to them 
> or otherwise play with them :-) You will need to gunzip them before 
> installing them, but I expect that's obvious ;)
> Also, don't forget to ensure you have set them executable first.
> chmod +x /usr/sbin/{mailscanner_create_locks,update_virus_scanners}
> (Yes, that really is a valid shell command).
>
> Once you have tested them and confirmed they set the ownerships 
> correctly, I'll re-release the latest stable MailScanner with this 
> important fix in it.
>
> Jules
>
Hummm ... when I run the following ... you see what I get?

/usr/sbin/update_virus_scanners LOCKDIR = 
'/var/spool/MailScanner/incoming/Locks'
RUNASU = 'postfix'
RUNASG = 'postfix'
/usr/sbin/update_virus_scanners: line 38: 
/tmp/tmp/usr/sbin/mailscanner_create_locks: No such file or directory

???


More information about the MailScanner mailing list