misc mailscanner questions. startup script related.

Julian Field mailscanner at ecs.soton.ac.uk
Tue Oct 8 17:15:29 IST 2002


I didn't realise the -T had made it into a distribution, I didn't intend it
to. I'll save that one for another day. 4a10-1 won't have the -T any more.

At 08:12 08/10/2002, you wrote:
>We figured out today why my mailscanner stop script was failing to kill my
>mailscanner processes.  The latest 4.00a9-7.tar has 'perl -I$virusdir -T
>$process $config' as the startup command in check_mailscanner.linux.  Now,
>this causes the 'killproc mailscanner' in the mailscanner startup script to
>not kill the processes.  (Mike changed this to 'killproc perl' earlier
>today, and while this successfully killed the mailscanner process, it also
>kill other perl services running on the box.  webmin, etc.)
>
>Now, I changed the 'perl -I$virusdir -T $process $config' in
>check_mailscanner.linux to '$process $config' as it was in 4.00a7, and
>changed to mailscanner startup script back to 'killproc mailscanner' and
>this all seems to work properly again.
>
>I made some modifications to my mailscanner startup script to make it a
>little more easily configurable, with some default setting in it for the tar
>release.  All the options are working for me again. (I also noticed that the
>pid files in the PIDDIR were not being deleted.  This script now deletes
>them.  My system did not like the [ -f /opt/MailScanner/var/* ] statement)
>
>I have put both of the files that I have modified up at:
>         http://www.acknak.org/mailscanner (startup script,
> /etc/init.d/mailscanner
>on redhat)
>         http://www.acknak.org/check_mailscanner.linux
>(/opt/MailScanner/bin/check_mailscanner.linux in tar release)
>
>Hope this helps any of you that may be having similar occurances.
>
>Kris
>
>-----Original Message-----
>From: MailScanner mailing list [mailto:MAILSCANNER at JISCMAIL.AC.UK]On
>Behalf Of Kris Stumpner
>Sent: Monday, October 07, 2002 1:37 PM
>To: MAILSCANNER at JISCMAIL.AC.UK
>Subject: Re: [MAILSCANNER] NDPM_File.pm / Locked message ?
>
>
>bingo.  That fixed the problems.  SpamAssassin works again (it was dying
>before) with no more errors/warnings.
>
>I managed to pull the new mailscanner script out of the redhat rpm, now to
>hack it up to make it work.  (very brief changing got it to start up
>mailscanner fine.  Shutting down mailscanner is still not working, and I get
>a './mailscanner: [: too many arguments' error, but I'll work on that for a
>bit and see if I can't come up with something.)
>
>Another thing that I have noticed between the tar release and the RPM
>release.  The majority of the filenames in the tar version are mailscanner
>(lowercase), whereas the filenames in the rpm release is MailScanner.  Not
>that I figure many people will be hopping back and forth between tar and rpm
>release, but I was just wondering if this was intentional.
>
>Thanks again,
>
>Kris
>
>-----Original Message-----
>From: MailScanner mailing list [mailto:MAILSCANNER at JISCMAIL.AC.UK]On
>Behalf Of Julian Field
>Sent: Monday, October 07, 2002 12:35 PM
>To: MAILSCANNER at JISCMAIL.AC.UK
>Subject: Re: [MAILSCANNER] NDPM_File.pm / Locked message ?
>
>
>At 16:56 07/10/2002, you wrote:
> >(The whole setup
> >is acting flakey, but that's where the problems is RIGHT now)
>
>:-(
>
> >   The
> >NDBM_File.pm error comes up as spamassassin starts. (And every once in a
> >while after that)
>
>It appears to be a problem with me doing a "require" versus a "use" on the
>SpamAssassin code where it sets up talking to the database file Perl code.
>
>I have added a line to the top of my SpamAssassin code to force it to load
>the database file code earlier. This appears to keep SpamAssassin quiet and
>gets rid of this warning.
>
>Build 7 is up on the web site with this correction in it.
>
> >I am using the tar distribution on my system.
> >Would it be possible to name the tar releases to coincide with the revision
> >number like the RPM release is so we can tell if we've got the latest one
> >up?
>
>Done.
>
> >Also.  Has the /etc/init.d/mailscanner script changed for v4?  The version
>I
> >have now (from a 3.2x rpm release) does not kill the daemon processes
> >properly (or at all).
>
>Getting this script right across different Linuxes, let alone different
>Unixes (Unices if you prefer) is nigh on impossible. The latest one seems
>to work pretty well though, give it a try.
>
> >-----Original Message-----
> >From: MailScanner mailing list [mailto:MAILSCANNER at JISCMAIL.AC.UK]On
> >Behalf Of Julian Field
> >Sent: Monday, October 07, 2002 6:15 AM
> >To: MAILSCANNER at JISCMAIL.AC.UK
> >Subject: Re: [MAILSCANNER] NDPM_File.pm / Locked message ?
> >
> >
> >At 02:58 07/10/2002, you wrote:
> > >I fixed the HTML-Parser.pm error finally, but now I get the following
>error
> > >when starting mailscanner.
> > >
> > >"Use of unitialized value in require at
> > >/usr/lib/perl5/5.6.1/i386-linux/NDBM_File.pm line 6."
> >
> >That is someone else's bug. Not my problem (yet) :-)
> >
> > >Then I get a 'Locked message' error at my console everytime a new email
> > >comes in.
> >
> >I just searched all my code for that message, and the call to print it is
> >commented out in the latest code.
> >
> > >Any Ideas on this one?
> >
> >Is it still doing it with newest release?
> >Are you using the tar distribution or the RPMs?
> >--
> >Julian Field                Teaching Systems Manager
> >jkf at ecs.soton.ac.uk         Dept. of Electronics & Computer Science
> >Tel. 023 8059 2817          University of Southampton
> >                              Southampton SO17 1BJ
>
>--
>Julian Field                Teaching Systems Manager
>jkf at ecs.soton.ac.uk         Dept. of Electronics & Computer Science
>Tel. 023 8059 2817          University of Southampton
>                              Southampton SO17 1BJ

--
Julian Field                Teaching Systems Manager
jkf at ecs.soton.ac.uk         Dept. of Electronics & Computer Science
Tel. 023 8059 2817          University of Southampton
                             Southampton SO17 1BJ



More information about the MailScanner mailing list