Directorys in /var/spool/MailScanner/incoming

[Ant La Porte]

Julian Field said:
> At 18:24 28/10/2002, you wrote:
>>On Mon, 2002-10-28 at 11:19, Julian Field wrote:
>> > At 16:50 28/10/2002, you wrote:
>> > >RedHat 7.2 and the rpm MailScanner 4.03-1
>> > >
>> > >Directorys with the same name as the pid are being created in
>> /var/spool/MailScanner/incoming, but are not being cleaned up on a
>> restart or stop - is this as it should be?.
>> > >Is their any resason I should not delete them in the stop and
>> restart parts of /etc/rc.d/init.d/MailScanner
>> >
>> > What do you think? Would you like me to extend the init.d script so
>> that it clears out MailScanner/incoming? Any good reasons for *not*
>> doing it?
>> >
>>It would seem to me that the only pid files that should be there are
>> those associated with what should be an active instance of MailScanner.
>> The way it appears to work now the list of pid files will essentially
>> grow without bound
>
> I'm not sure quite why this is. Need to take a look at the forking code
> again.
>

If it's any help I was seeing this behaviour up untill 4.01-8. Since then
the only directories in /var/spool/MailScanner/incoming correspond to the
active processes (same for the files in /opt/MailScanner/var). I'm using
the tarball version and check_mailscanner, modified to give options to
start|stop|restart but not so far that it intentionally deletes these
files and directories.


>>  and you can't tell from casual examination of the
>>directory which pid files correspond to an active process. I can see
>> where this might become a problem on a busy server where you only
>> stop/restart MailScanner when it is misbehaving rather than on a
>>regularly scheduled basis.
>
> Indeed.
> --
> 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


--
Ant La Porte - Dvere Network Services