Solaris 10 startup bug (still)

[Jeff A. Earickson]

Gang (especially fellow Solaris 10 users),

This is a bug that has been vexing me for a month or so, and I would
like to figure out how to trap it.  My /etc/init.d startup script just
causes MailScanner to loop without doing anything.  Syslog says:

MailScanner E-Mail Virus Scanner version 4.54.4 starting...
MailScanner[28182]: Read 719 hostnames from the phishing whitelist
MailScanner[28182]: Config: calling custom init function IPBlock
MailScanner[28182]: Initialising IP blocking
MailScanner[28182]: Read 128 IP blocking entries from /etc/MailScanner/IPBlock.conf
MailScanner[28182]: Using SpamAssassin results cache
MailScanner[28182]: Connected to SpamAssassin cache database
MailScanner[28182]: Expired 28 records from the SpamAssassin cache
(pause, repeat)

I see a bunch of MS processes out there spinning their tires, no email
gets processed.  If I launch MailScanner by hand from the terminal like so:

/opt/MailScanner/bin/MailScanner --debug /opt/MailScanner/etc/MailScanner.conf

it works fine.  Lint mode also works.  If I launch it like so:

/opt/MailScanner/bin/MailScanner /opt/MailScanner/etc/MailScanner.conf

it loops-up.  This is all that check_mailscanner basically does.  If
I let cron launch MailScanner, eg:

0,5,10,15,20,25,30,35,40,45,50,55 * * * * [ -x /opt/MailScanner/bin/check_mailscanner ] && /opt/MailScanner/bin/check_mailscanner >/dev/null 2>&1

This also works fine.  This is currently how I restart MS, but I would
like to figure out this bug so I can use my /etc/init.d script again.
Ideas?

Jeff Earickson
Colby College