[SSSD] Are sssd_dp errors worth reporting?
I've seen an occasional and (as of yet) impossible to reproduce dp
segfault with sssd 0.6-1. Would it be worth trying to track down? It
looked like there were patches merged to remove the dp process
entirely. When sssd_dp segfaults, the watchdog doesn't restart it and
bad things happen. That leads to nasty messages in syslog like:
Oct 9 18:20:01.122 nameobscured crond[6931]: pam_sss(crond:account):
Request to sssd failed.
Restarting sssd fixes the problem but this is a bit disconcerting. Is
master in shape to snapshot and build rpms from or should I wait for
the 0.7 release without sssd_dp? This is the second time we've seen
this since 0.6 was released but it is still a legit problem.
--
Jeff Schroeder
Don't drink and derive, alcohol and analysis don't mix.
http://www.digitalprognosis.com