Red Hat Bugzilla – Bug 247469
sealert running when SELinux disabled
Last modified: 2007-11-30 17:12:10 EST
I see that on a system where SELinux is disabled sealert is still started and it
is eating CPU cycles and causing wake ups. IMO sealert should check at start
whether SELinux is enabled or not and, if disabled, then just exit, not to waste
CPU and battery when there's nothing it can do.
Thank you for reporting this, it's an excellent suggestion and has been added to
the current code base.