I had an instance that
procmail has been running and taking up RAM. I am not using this. Is it possible to stop / uninstall this?
I am running CentOS 6.4.
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It only takes a minute to sign up.Sign up to join this community
Is there any reason why
killall procmail doesn't work?
If it's running as another user, try
sudo killall procmail
If procmail keeps on being restarted, that is because your Mail Transfer Agent (MTA - e.g. postfix or exim) keeps on invoking it to deliver mail to user inboxes. That's
procmail's job - it's a Mail Delivery Agent (MDA).
Some have suggested removing the
procmail package from your system. That will probably break your mail setup because your MTA is configured to use
procmail. If you do remove it, you'll also have to change the MTA config so that it doesn't use it.
A better solution is to examine your procmail rules files to find out which rule is causing procmail to misbehave. You'll want to examine system rule files (e.g. in
/etc/procmailrcs/) and in your own
~/.procmailrc file if you have one.
I can''t be any more specific than that because
procmail is a fairly full-featured mail processing language that's also capable of invoking external commands including other scripting interpreters like
perl, so the possibilities are endless.
If it's another user's .procmailrc, first find out which user it is with something like
ps -o pid,user,args -C procmail. Then either examine and fix (or comment out the broken rule in) their .procmailrc (if you are root) or inform the other user of the problem they are causing and/or inform the mail server admins.
Procmail is a so-called MDA, a mail delivery agent (a LDA [local delivery agent], to be precise). It delivers and filters emails when they arrive at the localhost.
This means that every time an email arrives on your box, procmail is run. If the procmail recipes of the user contain fancy stuff, procmail may well take up some RAM and CPU cycles. You should check the recipes in this case.
For details, please refer to
To remove a package, simply use
yum remove package_name
Be sure to check the dependencies before.