Hey everyone,
I've got a Buildroot FS and was trying to get 'system --user'
functionality working. I didn't have PAM installed (it wasn't
available in buildroot), but was informed that it was a must, so I
have added it to my system now. Pam seems to be working perfectly as
in I can log into the sy
On Sat, May 26, 2012 at 11:12 AM, Kok, Auke-jan H
wrote:
> which pam entry is this? /etc/pam.d/??
Just 'login' for now.. didn't want to keep breaking ssh by using other.
> this needs to be
>
> session optional pam_systemd.so ...
I tried that too and it didn't change anything, so I put it b
On Sat, May 26, 2012 at 10:00 PM, Shawn Ferris wrote:
>> 1) systemctl --system start user@.service (may not work, but is
>> usable as a template)
>> 2) ../user/default.target needs to define something meaningful
>> 3) "session optional pam_systemd.so" in /e
On Sun, May 27, 2012 at 1:05 AM, Kok, Auke-jan H
wrote:
> $ grep DBUS /usr/lib/systemd/system/user@.service
> Environment=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/%I/dbus/user_bus_socket
Yup.. had that
> $ cat /usr/lib/systemd/user/dbus.socket
> [Unit]
> Description=D-Bus System Message Bus
On Sun, May 27, 2012 at 1:13 AM, Kok, Auke-jan H
wrote:
> On Sun, May 27, 2012 at 5:51 AM, Shawn Ferris wrote:
>> On Sat, May 26, 2012 at 10:00 PM, Shawn Ferris
>> wrote:
>>>> 1) systemctl --system start user@.service (may not work, but is
>>>>
> It looks like dbus will need a patch upstream to work properly in the
> user session, so, I'm looking at that at this time.
Is this potentially why on boot, mine might work 1 out of every 30
boots or so? I thought it was timing (and I still believe it is, I
don't know with what), but I've set up
> It would help if you could post your unit files somewhere.
>
> tar up /usr/lib/systemd/user ?
Certainly.. here you go:
https://www.dropbox.com/s/8lxgh04jnpuecat/unit-files.tar.bz2
At this risk of not missing anything, I tar'd up all unit files..
including those included with the distro. And he
