Joe Smith wrote:
Scott Castaline wrote:
I am replying to my reply, because I am finally seeing the error that
Joe Smith mentions in my syslog file. I am kind of surprised that
this did not show up in the SELinux troubleshooter GUI like it
usually does. I was able to pull up the full explanation when I used
the CLI command sealert -l and then applying chcon -t to the file did
finally fix it. ...
Hey, nice work!
SELinux is a bit (big bit!) of a mystery to me also. Perhaps the
re-labeling has caused a problem with the troubleshooter GUI???
What are you referring to by "syslog file"? On my F7, there is no
syslog log file; all the system messages are in /var/log/messages or
/var/log/secure. Have you modified the configuration?
If you're really curious to find out what's happened, ask over on the
Fedora mailing list. There are some SELinux wizards there who seem
willing to help.
<Joe
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Blame it on the "OldTimerz" disease, syslog was a term we used for the
collection of log files that UNIX kept. It was actually
/var/log/messages. And yes I have gotten lazy with all these GUI's, and
used the System Log Viewer in F7. I was originally looking in the
security file thinking that SELinux is all about security, oh well.
Later I tried accessing a PDF file through FireFox, so when it tried to
access the Adobe Plugin I got the SE alert and the GUI did show the
error, so I don't know why it didn't for this issue. I need to go over
to FedoraForums anyway, as I've been informed by someone on the ALE list
(Atlanta Linux Enthusiasts) that there seems to be a flame war going on
about a similar problem whether or not it is an SELinux issue.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
