[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: core-updates call for testing
From: |
Ludovic Courtès |
Subject: |
Re: core-updates call for testing |
Date: |
Sun, 03 May 2020 21:57:05 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) |
Hi,
Marius Bakke <address@hidden> skribis:
> I see a similar failure when tracing the associated mingetty process:
>
> 1003 sendto(4, "<83>Apr 29 14:49:20 login[1003]: PAM unable to
> dlopen(/gnu/store/44il8dnl5qc6ryb3v0lp5374hg3h7vx5-elogind-243.4/lib/security/pam_elogind.so):
> /gnu/store/ahqgl4h89xqj695lgqvsaf6zh2nhy
> 4pj-glibc-2.29/lib/libc.so.6: version `GLIBC_2.30' not found (required by
> /gnu/store/44il8dnl5qc6ryb3v0lp5374hg3h7vx5-elogind-243.4/lib/security/pam_elogind.so)",
> 342, MSG_NOSIGNAL, NULL, 0) = 342
> 1003 getpid() = 1003
> 1003 sendto(4, "<83>Apr 29 14:49:20 login[1003]: PAM adding faulty module:
> /gnu/store/44il8dnl5qc6ryb3v0lp5374hg3h7vx5-elogind-243.4/lib/security/pam_elogind.so",
> 144, MSG_NOSIGNAL, NULL, 0) = 144
>
> Again running 'herd restart term-tty1' lets me log in successfully.
>
> I'm not sure what to do about this. Can we get the Shepherd to
> automatically restart select services on reconfigure?
As discussed on IRC, this issue is tracked here:
https://issues.guix.gnu.org/issue/32182
I don’t think it’s reasonable to automatically restart services that are
currently running; it should have terrible effects. Or maybe we could
mark services that are always safe to restart as such. But then,
‘term-tty1’ or ‘sshd’ are not always safe to restart, so it wouldn’t
help.
The bug report above proposes a relatively simple solution, which is to
not use the global /etc/pam directory to avoid the confusion.
Thanks,
Ludo’.