[systemd-devel] FW: Question about systemd sessions

2017-05-23 Thread Олег Гаврильченко
From: Олег Гаврильченко [mailto:gavrilche...@avionica.spb.ru] Sent: Monday, May 22, 2017 6:17 PM To: 'systemd-devel@lists.freedesktop.org' Subject: Question about systemd sessions Hello! I have question about systemd user sessions. When I start my

Re: [systemd-devel] FW: Question about systemd sessions

2017-05-23 Thread Mantas Mikulėnas
gdm registers its login screen as a session because it *is* in essence a regular (if trimmed down) GNOME session. It follows the same logind rules for accessing the display, audio out, etc. Various desktop services and recently even programs use DBus activation – instead of launching them

Re: [systemd-devel] how to correctly specify dependency on dbus

2017-05-23 Thread prashantkumar dhotre
Thanks. my service runs during early bootup. one intermittent issue I am seeing is that my service fails in dbus_bus_get_private() with error: 07:45:19 : dbus_bus_get_private() failed with error: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory dbus

Re: [systemd-devel] Locale setup for non-shells

2017-05-23 Thread Lennart Poettering
On Mon, 22.05.17 19:36, Nikolai Kondrashov (nikolai.kondras...@redhat.com) wrote: > On 05/22/2017 04:46 PM, Lennart Poettering wrote: > > On Mon, 22.05.17 14:11, Nikolai Kondrashov (nikolai.kondras...@redhat.com) > > wrote: > > > I'm trying to solve a problem of supplying locale settings to

Re: [systemd-devel] dbus and exit-on-idle

2017-05-23 Thread Colin Walters
On Sun, May 21, 2017, at 08:26 PM, Matthijs van Duin wrote: > I've been pondering how to allow my bus-activated service to exit when > it's unneeded (which is 99% of the time), and in particular how to deal > with exit/activate races correctly... See also

Re: [systemd-devel] dbus and exit-on-idle

2017-05-23 Thread Matthijs van Duin
On 22 May 2017 at 10:36, Lennart Poettering wrote: > Yes, the exit-on-idle logic on dbus is impossible to implement > correctly for non-trivial cases right now. > Hmm? Can you elaborate? Apart from the two issues I identified (which look easily fixable to me), are there