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.
Just noticed from the "top" command that one of my least heavily used box is swapping excessivly by a program called setroubleshootd. Following is the top section of the "top" command sorted by Swap used for both boxes.
Any idea why this is the case and what can I do about this?
Also tried checking it out to see if there's a "service setroubleshootd restart" but when I checked the status I got the following.
Code:
[root]# service setroubleshootd status
setroubleshootd: unrecognized service
Thanks but my CentOS version is 5.5 so doesn't look like it's due to an old setroubleshoot program. However, once I've turned on logging for setroubleshoot, I notice what's going into /var/log/setroubleshoot/setroubleshootd.log is essentially the same stuff that's being logged into /var/log/audit/audit.log with the following repeatedly. It looks like both "ifconfig" and "mii-tool" are trying to repeatedly access the /var/spool/mail area. Has anyone seen this? Why would these two network programs trying to access the mail files?
SELinux protects files from processes that shouldn't have access to them amongst other things. The above log just looks like loads of stuff is being denied access to files they might actually need access to. Although I'm not really sure why mii-tool or ifconfig are trying to read the mail spool? Perhaps they're trying to email root user.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.