Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm having an issue trying to keep Postfix grounded completely.
I'll run
postfix stop (from root)
and it'll successfully stop without any errors. But only for like 5 minutes...then it starts again on it's own. Seems like the Plesk install on it might be the culprit, and making it restart.
I read a site just now that a guy uninstalled postfix completely, and it caused his plesk install to fail. So I guess I don't want to uninstall it. Just to stop it completely.
I don't use email on the server.
I'm running a Linux/Unix - Centos .
my postfix starts at /etc/rc.d/init.d/postfix
config file is at /etc/postfix/master.cf and main.cf are both located there.
Like you said your plesk install keeps starting postfix and if that is the case then you have got two options:
1. Misconfigure postfix configuration file so that plesk is not able to start it at all. However, if plesk depends on or checks the exit status whether it was able to start postfix successfully or not then you have to go with option 2.
2. Create a watch dog script which will check postfix and put it in cron to run every minute (you can configure the script to check every 30 seconds with a little tweak that is adding sleep command). Example script to put it in cron:
Code:
#!/bin/bash
#Script to check postfix
service postfix status
if [ $? -eq 0 ]
then
{
service postfix stop
}
else
{
echo "Service postfix already stopped" > /dev/null
fi
If the Plesk application launches the Postfix daemon, the chkconfig line won't stop that.
IPtables rules wouldn't stop the Postfix daemon from running, but it would prevent e-mail from coming in and going out. That's not enough in this situation (not being snarky, just asking)?
chkconfig postfix off or chkconfig postfix on here is irrelevant the reason being postfix is triggered by plesk as you said. So if I will keep it off during startup eventually it will be turned on by plesk.
but their far and few between....like once every 3 minutes, and their not taking up any CPU. Is it normal for them to still show up on Top even though it's suppose to be disabled? It's taking up like no CPU, so that's good.
friggin process seems unstoppable, unless it's uninstalled.
blocking the firewall ports, might be why it's taking up no cpu now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.