"Dave Stern - Former Rocket Scientist" <dave(_at_)umiacs(_dot_)umd(_dot_)edu>
wrote:
[snip]
We're theorizing that the host was running out of processes and couldn't
fork spamc hanging these procmail processes. We therefore presume that
1/ If we pay attention to the order of rules we'll be better and
2/ If we increase number of processes (I think nproc in /etc/system(?))
this problem wont bother us again.
Anyone have any comments or seen something similar? Or know of a way to
limit number of procmail processes a user can run?
the way to go is to limit the number of process a user may have.
I use the following rule to limit the spamc (or whatever resource
eater process) by using a lock file whenever the process is running.
SA_MBOX=${MAILPRE}${MAILSEP}spam${MAILSEP}assassin${MAILSUF}
SA_LOCK=${PMDIR}/lock/spamassassin${LOCKEXT}
SA_FILTER="/usr/local/bin/spamc -x"
:0 fw: ${SA_LOCK}
* ! ^X-Spam-Status:
* ! ^X-Spam-Level:
* < 256000
| ${SA_FILTER}
:0:
* ^X-Spam-Status: Yes
${SA_MBOX}
this way, only one spamc process may be run by a user and the machine
doesn't go to the limbe (hang).
Cyrille Lefevre.
--
mailto:clefevre-lists(_at_)9online(_dot_)fr
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail