FS#59682 - cronie doesn't survive glibc upgrades
Attached to Project:
Community Packages
Opened by Drew DeVault (SirCmpwn) - Thursday, 16 August 2018, 19:29 GMT
Last edited by Eli Schwartz (eschwartz) - Thursday, 16 August 2018, 20:06 GMT
Opened by Drew DeVault (SirCmpwn) - Thursday, 16 August 2018, 19:29 GMT
Last edited by Eli Schwartz (eschwartz) - Thursday, 16 August 2018, 20:06 GMT
|
Details
Description:
After a glibc upgrade, cronie writes this to the console over and over and stops processing tasks: PAM unable to dlopen(/usr/lib/security/pam_unix.so): /usr/lib/libc.so.6: version `GLIBC_2.27' not found (required by /usr/lib/libgssapi_krb5.so.2) PAM adding faulty module: /usr/lib/security/pam_unix.so The service needs to be restarted after an upgrade. |
This task depends upon
Closed by Eli Schwartz (eschwartz)
Thursday, 16 August 2018, 20:06 GMT
Reason for closing: Not a bug
Thursday, 16 August 2018, 20:06 GMT
Reason for closing: Not a bug
What exactly are we supposed to do here, and how is cronie supposed to know when it needs to restart itself in response to a *different* package?
The only real systematic solution to this (aside for developing an Arch policy to restart all programs ever, just in case, on any update to any dependency), is to use sysadmin scripts like https://github.com/seblu/archutils/blob/master/checkservices and check for things like this.
There is really nothing to do here.