Bug#871688: exim4-base: using su in cronjob invokes a full pam-session. use runuser instead

Am 2017-08-14 um 16:30 schrieb Marc Haber: > On Thu, Aug 10, 2017 at 07:19:14PM +0200, Jakobus Schürz wrote: >> You find my changes below to use runuser instead of su, which solves the >> problems comming from the su-command. > > Given that I have never heard of runuser in 20+ years of Unix >

Bug#871688: exim4-base: using su in cronjob invokes a full pam-session. use runuser instead

On Thu, Aug 10, 2017 at 07:19:14PM +0200, Jakobus Schürz wrote: > You find my changes below to use runuser instead of su, which solves the > problems comming from the su-command. Given that I have never heard of runuser in 20+ years of Unix experience, shouldn't probably the su man page mention

Bug#871688: exim4-base: using su in cronjob invokes a full pam-session. use runuser instead

Am 2017-08-13 um 13:53 schrieb Andreas Metzler: > On 2017-08-13 Jakob Schürz wrote: >> Am 2017-08-11 um 14:58 schrieb Andreas Metzler: >>> On 2017-08-10 Jakobus Schürz wrote: > [...] # if we reach this, invoking exim_tidydb from

Bug#871688: exim4-base: using su in cronjob invokes a full pam-session. use runuser instead

Am 2017-08-11 um 14:58 schrieb Andreas Metzler: > On 2017-08-10 Jakobus Schürz wrote: >> Package: exim4-base >> Version: 4.89-2+deb9u1 >> Severity: normal > >> Dear Maintainer, > >> I have some systemd --user services from other packages. >> The units are located in

Bug#871688: exim4-base: using su in cronjob invokes a full pam-session. use runuser instead

On 2017-08-10 Jakobus Schürz wrote: > Package: exim4-base > Version: 4.89-2+deb9u1 > 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

Bug#871688: exim4-base: using su in cronjob invokes a full pam-session. use runuser instead

Package: exim4-base Version: 4.89-2+deb9u1 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