I'm trying to audit my user logs on my system but journalctl shows
nothing, saying
No journal files were opened due to insufficient permissions.
journald has created these files:
total 587,776
drwxr-xr-x 2 root root4 Oct 8 22:13 .
drwxr-xr-x 3 root root3
2013/10/9 Manuel Amador (Rudd-O) rud...@rudd-o.com:
I'm trying to audit my user logs on my system but journalctl shows nothing,
saying
No journal files were opened due to insufficient permissions.
journald has created these files:
total 587,776
drwxr-xr-x 2 root root4
Because that's exactly the kind of situation where the private bus is
necessary.
---
src/core/manager.c | 18 +++---
1 file changed, 11 insertions(+), 7 deletions(-)
diff --git a/src/core/manager.c b/src/core/manager.c
index 58dacdc..e183325 100644
--- a/src/core/manager.c
+++
It seems that some places use /run otherwise, which isn't going to work.
---
src/core/main.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/src/core/main.c b/src/core/main.c
index fe291f8..36543c6 100644
--- a/src/core/main.c
+++ b/src/core/main.c
@@ -1404,6 +1404,12 @@ int main(int
Your patch seems to be at odds with the commit message; since
DBUS_SESSION_BUS_ADDRESS won't be set for the user bus, we won't
attempt a connection, right?
What you're really trying to fix I assume is the warning systemd outputs
when it currently spawns user@?
Note I also patched this code in
On Wed, Oct 9, 2013 at 3:59 PM, Colin Walters walt...@verbum.org wrote:
Your patch seems to be at odds with the commit message; since
DBUS_SESSION_BUS_ADDRESS won't be set for the user bus, we won't
attempt a connection, right?
In the current code? Yes, but then it won't attempt to set up the
On Wed, Oct 2, 2013 at 8:12 PM, Auke Kok auke-jan.h@intel.com wrote:
These 2 mounts are allowed to fail, which will happen if the
system is not running a SMACK enabled kernel or security=none is
passed to the kernel.
The kernel throws errors for this at the console:
tmpfs: Bad mount
On Wed, Oct 9, 2013 at 9:18 AM, Kay Sievers k...@vrfy.org wrote:
On Wed, Oct 2, 2013 at 8:12 PM, Auke Kok auke-jan.h@intel.com wrote:
These 2 mounts are allowed to fail, which will happen if the
system is not running a SMACK enabled kernel or security=none is
passed to the kernel.
The
On Tue, Oct 8, 2013 at 3:29 PM, Schaufler, Casey
casey.schauf...@intel.com wrote:
-Original Message-
From: Lennart Poettering [mailto:lenn...@poettering.net]
Sent: Tuesday, October 08, 2013 3:17 PM
To: Kok, Auke-jan H
Cc: Zbigniew Jędrzejewski-Szmek; Schaufler, Casey; systemd-devel
Add a MemorySoftLimit setting that behaves the same way
as MemoryLimit, except that it controls the
memory.soft_limit_in_bytes cgroup attribute.
---
man/systemd.resource-control.xml | 7 ++-
src/core/cgroup.c | 14 ++
src/core/cgroup.h
Add a MemoryAndSwapLimit setting that behaves the same way
as MemoryLimit, except that it controls the
memory.memsw.limit_in_bytes cgroup attribute.
---
man/systemd.resource-control.xml | 9 +++--
src/core/cgroup.c | 21 ++---
src/core/cgroup.h
Add a KernelTcpMemoryLimit setting that behaves the same way
as KernelMemoryLimit, except that it controls the
memory.kmem.tcp.limit_in_bytes cgroup attribute.
---
man/systemd.resource-control.xml | 17 +
src/core/cgroup.c | 16
Add a KernelMemoryLimit setting that behaves the same way
as MemoryLimit, except that it controls the
memory.kmem.limit_in_bytes cgroup attribute.
---
man/systemd.resource-control.xml | 5 -
src/core/cgroup.c | 18 +-
src/core/cgroup.h
13 matches
Mail list logo
