Should logrotate be trying to access this?
If so why is not the proper policy in place for it?
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
On Wed, 2014-12-17 at 16:22 -0500, Robert Moskowitz wrote:
Should logrotate be trying to access this?
If so why is not the proper policy in place for it?
There is a very popular bug report on it, CC yourself on that.
https://bugzilla.redhat.com/show_bug.cgi?id=1163438
-- Adam Williamson
On 12/17/2014 04:24 PM, Adam Williamson wrote:
On Wed, 2014-12-17 at 16:22 -0500, Robert Moskowitz wrote:
Should logrotate be trying to access this?
If so why is not the proper policy in place for it?
There is a very popular bug report on it, CC yourself on that.
On Wed, Dec 17, 2014 at 1:47 PM, Robert Moskowitz r...@htt-consult.com wrote:
I really need to get better at searching bugzilla...
The SELinux troubleshooter report bug button did that for me. ;-)
--
Twitter: http://twitter.com/znmeb; OSJourno: Robust Power Tools for
Digital Journalists
On 12/17/2014 04:51 PM, M. Edward (Ed) Borasky wrote:
On Wed, Dec 17, 2014 at 1:47 PM, Robert Moskowitz r...@htt-consult.com wrote:
I really need to get better at searching bugzilla...
The SELinux troubleshooter report bug button did that for me. ;-)
Oh, I am having other problems like with
No, but report a bug on it and include relevant details as to what you were
doing that triggered this.
Dan
On Thu, Apr 19, 2012 at 9:36 AM, Fernando Cassia fcas...@gmail.com wrote:
Should I be worried about this?
SELinux is preventing useradd from write access on the directory /run.
*
On 19/04/12 17:36, Fernando Cassia wrote:
Should I be worried about this?
SELinux is preventing useradd from write access on the directory /run.
https://admin.fedoraproject.org/mailman/listinfo/selinux
Dan and Misoslav (apologies for spelling)
They tend to be fairly active there,
on above
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/19/2012 12:47 PM, Frank Murphy wrote:
On 19/04/12 17:36, Fernando Cassia wrote:
Should I be worried about this?
SELinux is preventing useradd from write access on the directory /run.
On Thu, Apr 19, 2012 at 17:24, Daniel J Walsh dwa...@redhat.com wrote:
What is useradd trying to write on /run?
Absolutely no idea, and what I pasted was the ´details´ view of the Selinux
alert dialog. But since I was running lots of software at the time, it´s a
bit difficult to tell
