New answers tagged selinux
GAH export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig And suddenly (c)make can find the packages...
Your file has the immutable extended attribute set, which is why you can't delete it. lsattr returns the extended attributes on the file: $ lsattr model/DailyUpdateClass.class -u-Diad--j------ DailyUpdateClass.class You will need to decipher all of the letters (-u-Diad--j) The man page for lsattr will tell you to look at the man page for chattr for a ...
A number of possibilities: the trailing dot in the file permissions line -rwSr-s---. indicate extended permissions, either SE Linux (confirm with ls -lZ) or ACL style permissions (confirm with getfacl ) which may block root overrides. the file has been made immutable with chattr ; confirm the file system attributes with lsattr The file is on a NFS ...
It seems that this is how it should be: From changelog of selinux-policy-3.12.1-139: - Allow systemd_cronjob_t to be entered via bin_t Do you have any errors in /var/log/audit/audit.log pertaining to mariadb? A quick and easy check is to setenforce=0 and run your cron jobs. If they fare better then it was SELinux causing the issue.
Disabling SELinux without reboot is not possible. But I guess making it in permissive mode is going to satifsy your requirement. The output of sestatus shows SELinux is enabled but also shows it is in Permissive mode, which is what you just did with the setenforce command.
sestatus is showing the current mode as permissive. In permissive mode, SELinux will not block anything, but merely warns you. The line will show enforcing when it's actually blocking. I don't believe it's possible to completely disable SELinux without a reboot.
Sorry, I have found the reason. This is totally because of the SSL CERT problem. Not really because of above notices. How do I do was that I enabled the Apache Detailed Logs and then that's the real move. It shows what really is happening, by showing the Failure at the loading of mod_ssl module, while starting the Apache. Then I realized it is because of ...
To begin with, Linux is not at all about security; the Linux maintainers are not particularly interested in security. Second, SELinux is an implementation of a security model developed at the University of Utah, and the NSA just provided an open source implementation of that. Finally, despite all else that justly can be said about the NSA, SELinux is a ...
Top 50 recent answers are included