On Sun, Feb 16, 2014 at 12:03:21AM +0100, Djalal Harouni wrote:
Currently systemd-nspawn will call reset_audit_loginuid() and check
if audit is enabled in the kernel even if it was invoked without the
--boot argument. This makes systemd-nspawn print the audit error message
and sleep(5) on
On Sun, 16.02.14 00:03, Djalal Harouni (tix...@opendz.org) wrote:
Currently systemd-nspawn will call reset_audit_loginuid() and check
if audit is enabled in the kernel even if it was invoked without the
--boot argument. This makes systemd-nspawn print the audit error message
and sleep(5) on
On Sun, 16.02.14 17:40, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
On Sun, Feb 16, 2014 at 12:03:21AM +0100, Djalal Harouni wrote:
Currently systemd-nspawn will call reset_audit_loginuid() and check
if audit is enabled in the kernel even if it was invoked without the
--boot
On Sun, Feb 16, 2014 at 10:14:00PM +0100, Lennart Poettering wrote:
On Sun, 16.02.14 17:40, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
On Sun, Feb 16, 2014 at 12:03:21AM +0100, Djalal Harouni wrote:
Currently systemd-nspawn will call reset_audit_loginuid() and check
if
Currently systemd-nspawn will call reset_audit_loginuid() and check
if audit is enabled in the kernel even if it was invoked without the
--boot argument. This makes systemd-nspawn print the audit error message
and sleep(5) on every execution.
This was introduced by commit db999e0f923ca6. Fix it