Description of problem:
Version-Release number of selected component (if applicable):
My serial console is filled with junk on reboot because setroubleshootd prints
messages about errors as attached.
Steps to Reproduce:
1.Boot up a box now running selinux (permissive), but that formerly had it
disabled and then went through an install from scratch, preserving /home et al
Lots of noise to the console, as attached
No such noise, that represents programming errors
Created attachment 133693 [details]
Noise printed to the console, or to the tty where the setroubleshoot service is started
There was a 64 bit problem in the code, which has been fixed in this release.
I'm not sure whether this is the same problem or a different one, but 0.41-1
still eats lots of CPU and, worse, it also eats all memory. It managed to
exhaust the more than 4GB of swap I had on my firewall. I've relabeled
everything but an alternate / for FC5 that I keep mounted and up-to-date, and it
still doesn't like me for some reason. This happens to 4 different x86_64
boxes. I haven't really tried it on x86_32. Any tips on how to figure out
what's going on?
Re: comment #3, this is a different bug, the one in this bug report was 64 bit
specific and has been fixed, I'm closing this bug.
However, what you are seeing Alexandre are two known problems. The memory usage
bug 204274, and cpu consuption is bug 206050.
I'm going to close this as fixed in rawhide because the original bug was a 64
bit specific issue. Alexandre's observation are duplicates of 204274 and 206050.