On Wed, Dec 10, Konrad Rzeszutek Wilk wrote:
On Mon, Dec 08, 2014 at 11:18:05AM +0100, Olaf Hering wrote:
This is a resend of this series, with just the low hanging fruits:
http://lists.xenproject.org/archives/html/xen-devel/2014-12/msg00669.html
This looks like it would fix some of the
On Thu, Dec 11, M A Young wrote:
Yes, you do need to set explicit selinux permissions when mounting
/var/lib/xenstored as otherwise it gets a tmpfs selinux context which
xenstored can't use in enforcing mode.
Is that enforcing mode the default? And would it be too cumbersome to
have these
On Thu, Dec 11, Olaf Hering wrote:
This sounds like xenstored has to parse the possible environment
variables found in sysconfig.xencommons all by itself? Is there perhaps
a way out of the SELinux jail?
Does all that work with the sysv runlevel scripts?
Olaf
On Thu, 11 Dec 2014, Olaf Hering wrote:
On Thu, Dec 11, Olaf Hering wrote:
This sounds like xenstored has to parse the possible environment
variables found in sysconfig.xencommons all by itself? Is there perhaps
a way out of the SELinux jail?
Does all that work with the sysv runlevel
On Thu, Dec 11, 2014 at 01:04:24PM +0100, Olaf Hering wrote:
On Thu, Dec 11, M A Young wrote:
Yes, you do need to set explicit selinux permissions when mounting
/var/lib/xenstored as otherwise it gets a tmpfs selinux context which
xenstored can't use in enforcing mode.
Is that
On Mon, Dec 08, 2014 at 11:18:05AM +0100, Olaf Hering wrote:
This is a resend of this series, with just the low hanging fruits:
http://lists.xenproject.org/archives/html/xen-devel/2014-12/msg00669.html
This looks like it would fix some of the issues I saw. I will test it
over today.
Please
This is a resend of this series, with just the low hanging fruits:
http://lists.xenproject.org/archives/html/xen-devel/2014-12/msg00669.html
The mentioned wrapper to run xenstored from systemd without duplicate
functionality found in the sysv runlevel script will be send in another patch,
once it
