Hi *
I just moved my ArchLinux based server from systemd37 to 39.
Basically all went well.
For successful logging via rsyslog I do following:
1.symlink /lib/systemd/system/rsyslog.service to
/etc/systemd/system/rsyslog.service
2.added in rsyslog.conf entry $SystemLogSocketName
On Fri, 27.01.12 12:46, Warpme (war...@o2.pl) wrote:
Hi *
I just moved my ArchLinux based server from systemd37 to 39.
Basically all went well.
For successful logging via rsyslog I do following:
1.symlink /lib/systemd/system/rsyslog.service to
/etc/systemd/system/rsyslog.service
2.added
On Wed, 25.01.12 21:20, Mike Kazantsev (mk.frag...@gmail.com) wrote:
Good day,
Problem is that systemd-loginctl activate session-id gives
something like D-Bus call failed: Operation not permitted, while
strace of logind process looks like this:
epoll_wait(4, {{EPOLLIN, {u32=3,
On Wed, 25.01.12 21:52, Mike Kazantsev (mk.frag...@gmail.com) wrote:
From c48f23ae82a8efac59f025e2534a97754b279f60 Mon Sep 17 00:00:00 2001
From: Mike Kazantsev mk.frag...@gmail.com
Date: Wed, 25 Jan 2012 21:24:02 +0600
Subject: [PATCH] build-sys: add creation of /var/lib/systemd path, used
Hi,
I am wondering if there is a dbus API equivalent of sd_pid_get_session from
sd-login.h I know ConsoleKit provides a dbus API for it but I couldn't find
something similar in login1 dbus interface. AIUI login1 is the future so just
want to make sure I'm not using anything deprecated.
Reason
