Yes,
I've installed it on a LinuxFromScratch system, I've mentioned earleir.
I've solved it, indeed the rebuild of dbus with the right parameter
was required. That solved it.
Stef Bon
2011/7/25 Lennart Poettering :
> On Mon, 25.07.11 13:27, Stef Bon ([email protected]) wrote:
>
>> systemd-login
On Mon, 25.07.11 13:27, Stef Bon ([email protected]) wrote:
> systemd-logind[1948]: Failed to get system D-Bus connection: Failed to
> connect to socket /var/run/dbus/system_bus_socket: No such file or
> directory
> systemd-logind[1948]: Failed to fully start up daemon: Connection refused
> kernel
2011/7/25 Honza Horak :
> Hi,
>
> I'm wondering how good systemd is in killing all sub-processes when a
> service fails/ends (un)expectedly. Let's say a service forks several times
> during its execution and the forked processes do some nasty work to detach
> from parent process. Can we be sure tha
Hi,
I'm wondering how good systemd is in killing all sub-processes when a
service fails/ends (un)expectedly. Let's say a service forks several
times during its execution and the forked processes do some nasty work
to detach from parent process. Can we be sure that all processes will be
interr
Hi,
I added the pammodule to the system -auth stack, in various pam
service files, like kdm, su and sshd, and got the
error:
kdm: :0[2244]: pam_systemd(kde:session): Failed to create session:
Launch helper exited with unknown return code 1
sshd[4221]: pam_systemd(sshd:session): Failed to create
