SMPID vs. INPID

Alden Levy alden at engineno9inc.com
Wed May 9 15:49:17 IST 2007


Scott Silva ssilva wrote on Wed May 9 04:40:53 IST 2007
>Alden Levy spake the following on 5/8/2007 7:39 PM:
>>> Scott Silva ssilva wrote on Wed May 9 00:17:19 IST 2007
>>>> Scott Silva ssilva wrote on Tue May 8 21:08:43 IST 2007
>>>>> Alden Levy spake the following on 5/8/2007 12:16 PM:
>>>>>> Hugo van der Kooij wrote on Tue May 8 20:09:32 IST 2007
>>>>>>> On Tue, 8 May 2007, Alden Levy wrote:
>>>>>>>
>>>>>>>> Thanks for this.  Now, I'm really confused; the RedHat init script
is
>>>>>>>> identical to the one I'm using.
>>>>>>>>
>>>>>>>> Does anyone have an idea of where else I should look? (Quick recap:
>>>>>>>> /var/run/sendmail.in.pid is not getting updated, so
>>>>>>>> /etc/init.d/MailScanner
>>>>>>>> status lists incoming sendmail as failed.  sm-client.pid looks
fine,
>>>>>>>> though.)
>>>>>>> If you stop MailScanner the PID file should be gone. If not then you

>>>>>>> should remove it by hand and see if it happens to get recreated at 
>>>>>>> startup.
>>>>>>>
>>>>>>> Hugo.
>>>>>>>
>>>>>>> -- 
>>>>>>> 	hvdkooij at vanderkooij.org	http://hugo.vanderkooij.org/
>>>>>>> 	    This message is using 100% recycled electrons. 
>>>>>> Well, that was a mistake!  Now after removing the file by hand, and
>>>>>> restarting, I run status and get:
>>>>>> Checking MailScanner daemons:
>>>>>>          MailScanner:                                      [  OK  ]
>>>>>>          incoming sendmail: head: cannot open
>> `/var/run/sendmail.in.pid' for
>>>>>> reading: No such file or directory
>>>>>>                                                            [FAILED]
>>>>>>          outgoing sendmail:                                [  OK  ]
>>>>>>
>>>>>>
>>>>>> Any other thoughts?
>>>>>>  Thanks,
>>>>>> Alden
>>>>>
>>>> Your init script could be either damaged, or an old version. 
>>>> But I did a diff on my init script and the RedHat script you sent
earlier 
>>>> today, and there is no difference.  Can it still be corrupted?
>>>>
>>>> I was wondering if I should look elsewhere, or just try to reinstall.
>>>>
>>>> Thanks,
>>>> Alden
>>>>
>>> You do have sendmail disabled, don't you?
>> 
>> Yep.  But I'm going to double check, anyway.  I've done "chkconfig
sendmail
>> off" a few times, but I'll try again.
>> 
>> However, when I start sendmail, I have 3 instances running:
>> # ps aux|grep sendmail
>> root     23940  0.0  0.0  9092 1888 ?        Ss   22:36   0:00 sendmail:
>> accepting connections
>> 
>> smmsp    23944  0.0  0.0  6940 1656 ?        Ss   22:36   0:00 sendmail:
>> Queue runner at 00:15:00 for /var/spool/clientmqueue
>> root     23949  0.0  0.0  8296 1780 ?        Ss   22:36   0:00 sendmail:
>> Queue runner at 00:15:00 for
>> /home/virtual/FILESYSTEMTEMPLATE/services/sendmail/mqueue
>> 
>> The first one doesn't stop when I service MailScanner stop, and I have to
>> issue a service sendmail stop in order to kill it.
>> 
>> Curiouser and curiouser... Is this good/bad/indifferent?  I've been
seeing
>> this for a while, as this was what I had on my old server, but I don't
>> remember what was running when it was working properly.
>> 
>> 
>Look in /etc/sysconfig for a MailScanner.rpmnew. Maybe you have an old
version
>in there.

I've looked, and there is no MailScanner.rpmnew in /etc/sysconfig.  The
original file has a date stamp of Feb 1, which predates my server setup, but
I *believe* is the date of the release of the version I'm using.  

Here's the file contents (with settings for other MTAs removed):
# Put in here all the settings for your particular mail system so that
# MailScanner's init.d script can run it all for you.
#

#
# Are you running Postfix, sendmail, Exim or ZMailer?
#
# Don't set it by hand, we now auto-detect it from MailScanner.conf
# MTA=sendmail
# MTA=postfix
# MTA=exim
# MTA=zmailer
# Extract setting for MTA from MailScanner.conf
MTA=`perl -n -e 'print "$_" if chomp && s/^\s*MTA\s*=\s*([a-zA-Z]+)/$1/ &&
($_=lc($_))' /etc/MailScanner/MailScanner.conf`

#
# Cron job update_virus_scanners settings
#
UPDATEMAXDELAY=600 # Maximum delay before running cron job to avoid server
peaks

#
# Cron job sa-update settings
#
SAUPDATE=/usr/bin/sa-update # Location of sa-update program

#
# MailScanner Settings
#
#WORKDIR=/var/spool/MailScanner/incoming # Where the temp MailScanner files
live
# Extract settings for "Incoming Work Dir" and "Incoming Queue Dir"
WORKDIR=`perl -n -e 'print "$_" if chomp &&
s/^\s*Incoming\s*Work\s*Dir\s*=\s*(\S+)/$1/i'
/etc/MailScanner/MailScanner.conf`
INQDIR=`perl -n -e 'print "$_" if chomp &&
s/^\s*Incoming\s*Queue\s*Dir\s*=\s*(\S+)/$1/i'
/etc/MailScanner/MailScanner.conf`
QUARDIR=`perl -n -e 'print "$_" if chomp &&
s/^\s*Quarantine\s*Dir\s*=\s*(\S+)/$1/i' /etc/MailScanner/MailScanner.conf`
RUNAS=`perl -n -e 'print "$_" if chomp &&
s/^\s*Run\s*As\s*User\s*=\s*(\S+)/$1/i' /etc/MailScanner/MailScanner.conf`
RESTART_DELAY=10 # Pause time between stop and start when restarting

#perl -e 'print "***WORKDIR='$WORKDIR'***\n***INQDIR='$INQDIR'***\n";'

#
# Sendmail Settings
#
SENDMAIL=/usr/sbin/sendmail
QUEUETIME=15m
#INQDIR=/var/spool/mqueue.in
INPID=/var/run/sendmail.in.pid
OUTPID=/var/run/sendmail.out.pid
SMPID=/var/run/sm-client.pid
MSPUSER=smmsp  # User for mail submission queue runner
MSPGROUP=smmsp # Group for mail submission queue runner

Thanks,
Alden



More information about the MailScanner mailing list