breakage between 4.68.5 and 4.68.8

Thu Apr 3 19:32:36 UTC 2008

>>> Put the location of the MailScanner.conf on the command-line and it should 
>>> be happier.
>>> At that point it doesn't know where the conf file is.
>>> I'll try to sort this for the next release.
>> 
>> Still sifting thu email, found this...  I start MailScanner via my
>> /etc/init.d script, the start portion looks like so (Solaris 10 here):
> I assume you have it properly setup as a service and start and stop it with
> svcadm enable site/mailscanner
> and
> svcadm disable site/mailscanner
> ?

I am using a legacy start/stop script in /etc/init.d, didn't see the
need for the complexity of SMF.

>> 
>> MSDIR=/opt/MailScanner
>> case "$1" in
>> start)
>>     su - root -c "$MSDIR/bin/check_mailscanner"
>>     status=$?
>>     ;;
>> 
>> So I went and looked at check_mailscanner.  It has:
>> 
>> process=MailScanner
>> msbindir=/opt/MailScanner/bin
>> config=/opt/MailScanner/etc/MailScanner.conf
>> 
>> so config matches where my MailScanner.conf file really lives, unless
>> symlinks have suddenly quit working.  And I don't think they have.
>> 
>> Jeff Earickson
>> Colby College
> And what happens when you run MailScanner --lint with the location of the 
> MailScanner.conf on the command-line, like this:
> /opt/MailScanner/bin/MailScanner --lint /opt/MailScanner/etc/MailScanner.conf
> ?

Getting the $ConfFile path specified correctly at line 768 of CustomConfig.pm
certainly helps, and the lint test above works correctly even if the patch
to CustomConfig.pm is pulled out.  So, as long as MailScanner gets invoked
with the correct path to MailScanner.conf spelled out, things work.  But
I invoke MailScanner via my boot script, which uses check_mailscanner and
has "$process $config" in there to specify the conf file path, and then it
doesn't work.  <head scratch>  check_mailscanner hasn't changed in ages.

I am now running 4.68.8 with the patch and the correct conf path in
CustomConfig.pm.  But I don't really know what broke.

Jeff Earickson
Colby College