On Sat, 02.05.15 07:01, Stephen Gallagher (sgall...@redhat.com) wrote:
Well, I guess for now. But note that eventually we hope to move most
programs invoked from .desktop into this as systemd services. This
then means that the actual sessions will become pretty empty, with
only stubs
On Fri, 01.05.15 08:29, Stephen Gallagher (sgall...@redhat.com) wrote:
Right, so based on this information, it seems to me that in SSSD we
need to be treating the 'systemd-user' PAM service the same way we do
the 'cron' service. The idea being that this is meant to handle
actions performed
On May 2, 2015, at 3:48 AM, Lennart Poettering lenn...@poettering.net wrote:
On Fri, 01.05.15 08:29, Stephen Gallagher (sgall...@redhat.com) wrote:
Right, so based on this information, it seems to me that in SSSD we
need to be treating the 'systemd-user' PAM service the same way we do
Stephen Gallagher wrote on 30/04/15 14:04:
On Thu, 2015-04-30 at 15:01 +0200, Lennart Poettering wrote:
On Thu, 30.04.15 08:54, Stephen Gallagher (sgall...@redhat.com)
wrote:
Does set-linger persist across reboots?
Yes it does. When a systemd is booted up with a user that has
lingering
On Fri, May 01, 2015 at 09:46:26AM +0100, Colin Guthrie wrote:
Stephen Gallagher wrote on 30/04/15 14:04:
On Thu, 2015-04-30 at 15:01 +0200, Lennart Poettering wrote:
On Thu, 30.04.15 08:54, Stephen Gallagher (sgall...@redhat.com)
wrote:
Does set-linger persist across reboots?
Yes
On Fri, 2015-05-01 at 11:46 +0200, Tomasz Torcz wrote:
On Fri, May 01, 2015 at 09:46:26AM +0100, Colin Guthrie wrote:
Stephen Gallagher wrote on 30/04/15 14:04:
On Thu, 2015-04-30 at 15:01 +0200, Lennart Poettering wrote:
On Thu, 30.04.15 08:54, Stephen Gallagher (sgall...@redhat.com)
On Thu, 2015-04-30 at 15:01 +0200, Lennart Poettering wrote:
On Thu, 30.04.15 08:54, Stephen Gallagher (sgall...@redhat.com)
wrote:
Does set-linger persist across reboots?
Yes it does. When a systemd is booted up with a user that has
lingering on this means that his user@.service
On Thu, 30.04.15 08:54, Stephen Gallagher (sgall...@redhat.com) wrote:
Does set-linger persist across reboots?
Yes it does. When a systemd is booted up with a user that has
lingering on this means that his user@.service instance is invoked at
boot, without waiting for any login.
Lennart
--
On Thu, 2015-04-30 at 11:36 +0200, Lennart Poettering wrote:
On Wed, 29.04.15 22:24, Jakub Hrozek (jakub.hro...@posteo.se) wrote:
...why exactly does systemd-user need to call the account stack
for? Again,
I totally understand session, but account?
Well, if the user service is started
On 10.04.2015 17:31, Lennart Poettering wrote:
On Fri, 10.04.15 17:20, Jakub Hrozek (jakub.hro...@posteo.se) wrote:
On 10.04.2015 17:06, Lennart Poettering wrote:
On Fri, 10.04.15 16:56, Jakub Hrozek (jakub.hro...@posteo.se) wrote:
I'm wondering why does systemd-user call the account
10 matches
Mail list logo
