Description of problem:
We use nss module winbind as our Linux hosts are joined to AD. When a software upgrade is done on winbind, and winbind is replaced, we restart winbind, but if crond previously loaded the old nss-winbind library because it was executing user jobs, then when the new module is put into place, crond will segfault each time it tries to run user jobs.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start crond
2. Make crond execute a job for a user who is in AD
3. Update nss-winbind library
4. Wait for cron to execute the next cron job. It will segfault.
I would expect that crond would close and re-open the nss library between runs.
If I restart crond after replacing winbind, there is no problem.