Hi, I'm working on a display-manager for a multiseat environment. Here is how we use logind
1. create new seat through udev 2. we set the XDG_SEAT in pamenv before calling pam_open_session() 3. we take XDG_SESSION_ID, XDG_RUNTIME_DIR and DBUS_SESSION_BUS_ADDRESS from pam_systemd Let say if a user already have a session(session0) in a seat (customseat0) and he want to start another session in another seat (customseat1). Our display manager would get the same DBUS_SESSION_BUS_ADDRESS from pam_systemd for session1. As we cannot use the same address for two sessions, we have to start dbus-session manually. Using the address provided by dbus-session as DBUS_SESSION_BUS_ADDRESS, we then proceed with starting gnome-keyring and gnome-session. Problem is, processes forked by 'systemd --user' will have DBUS_SESSION_BUS_ADDRESS="unix:path=$XDG_RUNTIME_DIR/bus" but processes forked by gnome-session will have DBUS_SESSION_BUS_ADDRESS=$DBUS_SESSION_PROVIDED_ADDRESS. Is there any way to make pam_systemd provides uniq DBUS_SESSION_BUS_ADDRESS for every session (may be unix:path=$XDG_RUNTIME_DIR/$XDG_SESSION_ID/bus)? or is there any way to ask 'systemd --user' to provide different DBUS_SESSION_BUS_ADDRESS to the childs? Thanks, Mohan R
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
