Bug#871969: leafnode: using su in cronjob runs pam_systemd, starts a whole session, causes errors

2017-09-23 Thread Jakobus Schürz
Am 2017-09-23 um 13:08 schrieb Ritesh Raj Sarraf: > Hello Jakobus, > > On Thu, 2017-09-07 at 21:06 +0200, Jakobus Schürz wrote: >>> >>> I am currently testing with the changes you've mentioned (And would >>> like to move to a socket based setup). >> >> For sure :-) >> >> Here are all my units for

Bug#871969: leafnode: using su in cronjob runs pam_systemd, starts a whole session, causes errors

2017-09-23 Thread Moritz Mühlenhoff
On Sat, Sep 23, 2017 at 04:53:29PM +0545, Ritesh Raj Sarraf wrote: > Hello Jakobus, > > On Thu, 2017-09-07 at 21:06 +0200, Jakobus Schürz wrote: > > > > > > I am currently testing with the changes you've mentioned (And would > > > like to move to a socket based setup). > > > > For sure :-) > >

Bug#871969: leafnode: using su in cronjob runs pam_systemd, starts a whole session, causes errors

2017-09-23 Thread Ritesh Raj Sarraf
Hello Jakobus, On Thu, 2017-09-07 at 21:06 +0200, Jakobus Schürz wrote: > > > > I am currently testing with the changes you've mentioned (And would > > like to move to a socket based setup). > > For sure :-) > > Here are all my units for leafnode: > Thank you very much. With your setup in

Bug#871969: leafnode: using su in cronjob runs pam_systemd, starts a whole session, causes errors

2017-09-07 Thread Jakobus Schürz
On Mon, 28 Aug 2017 20:47:40 +0530 Ritesh Raj Sarraf wrote: > Hello Jakbous, > > On Mon, 2017-08-28 at 13:07 +0200, Jakbous Schürz wrote: > > I wrote a socket-Unit for systemd, because I don't use inetd. > > > > Would you be kind to share your, working, socket based unit file

Bug#871969: leafnode: using su in cronjob runs pam_systemd, starts a whole session, causes errors

2017-08-28 Thread Ritesh Raj Sarraf
Hello Jakbous, On Mon, 2017-08-28 at 13:07 +0200, Jakbous Schürz wrote: > I wrote a socket-Unit for systemd, because I don't use inetd. > Would you be kind to share your, working, socket based unit file for leafnode ? IIRC, long back there was some effort by the leafnode maintainer to add

Bug#871969: leafnode: using su in cronjob runs pam_systemd, starts a whole session, causes errors

2017-08-28 Thread Jakbous Schürz
Am 2017-08-27 11:23, schrieb Ritesh Raj Sarraf: On Sun, 2017-08-13 at 07:17 +0200, Jakobus Schürz wrote: I have some systemd --user services from other packages. The units are located in /etc/systemd/user/ or /usr/lib/systemd/user/ and enabled on installing. When a daemon uses su or sudo on

Bug#871969: leafnode: using su in cronjob runs pam_systemd, starts a whole session, causes errors

2017-08-27 Thread Ritesh Raj Sarraf
On Sun, 2017-08-13 at 07:17 +0200, Jakobus Schürz wrote: > I have some systemd --user services from other packages. > The units are located in /etc/systemd/user/ or /usr/lib/systemd/user/ > and enabled on installing. > > When a daemon uses su or sudo on debian, it starts a service >

Bug#871969: leafnode: using su in cronjob runs pam_systemd, starts a whole session, causes errors

2017-08-12 Thread Jakobus Schürz
Package: leafnode Version: 1.11.10-3 Severity: normal Dear Maintainer, I have some systemd --user services from other packages. The units are located in /etc/systemd/user/ or /usr/lib/systemd/user/ and enabled on installing. When a daemon uses su or sudo on debian, it starts a service