Bug#825995: systemd: slow boot: pam_systemd(su:session): Failed to create session: Connection timed out

Vincent Lefevre vincent at vinc17.net
Wed Jun 1 11:51:24 BST 2016


On 2016-06-01 11:35:42 +0200, Michael Biebl wrote:
> Am 01.06.2016 um 10:40 schrieb Vincent Lefevre:
> 
> > This is part of one of my /etc/network/if-up.d scripts, where I have
> > "su vinc17 -c some_script" (which just does a rewrite of one of my
> > config files).
> 
> You are involving the pam stack here at a point when dbus is not
> available yet. So this is a misconfiguration of sorts.
> 
> I think you really want runuser instead of su here.

Thanks. I confirm that replacing "su" by "runuser" solves the issue.

But I've requested that the fact that su may not work at boot time
be documented in the su(1) man page (and suggest runuser instead):

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826003

-- 
Vincent Lefèvre <vincent at vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)




More information about the Pkg-systemd-maintainers mailing list