2014-11-19 19:32 GMT+08:00 Wang Jian <[email protected]>: > > 2014-11-19 18:07 GMT+08:00 intrigeri <[email protected]>: > >> Hi, >> >> Wang Jian wrote (19 Nov 2014 03:28:40 GMT) : >> > However, here I am struggling with user services. I have 3 jessie hosts, >> > all rolling upgrade from wheezy (one is a linode VPS). >> >> > root@gw:~# su - lark >> > lark@gw:~$ systemd-run --user /bin/ls >> > Failed to create bus connection: Connection refused >> >> Do you have a "systemd --user" instance running as the "lark" user? >> > > Yes. > > # loginctl enable-linger lark > > >> >> Do you have a D-Bus daemon running as the "lark" user? >> > > No. > > No dbus daemon running as 'lark'. I did try as > > https://wiki.archlinux.org/index.php/Systemd/User#D-Bus > > but without success. > > >> >> Has your session a valid $DBUS_SESSION_BUS_ADDRESS ? >> > > No. > > I remotely ssh login as root then su - lark. > > I guess it's a PAM configuration problem but I am still trying to > understand the whole picture. > > >> >> Does pam-auth-update show "Register user sessions in the systemd >> control group hierarchy" as enabled? >> > > Yes. > > My use case is a little special. I want to use it to replace > daemontools-run, to > run services of normal privilege on the servers, not for this single user. > > intrigeri,
It works if I login as 'lark'. So my situation is not related this bug. 'su - <username>' or 'sudo -i -u <username>' is not a new systemd session. I can confirm this by checking cgroup $ cat /proc/$$/cgroup This may or may not be another bug or mis-configuration of default installation. Thanks for your help.
