Gerald (Jerry) Carter wrote:
But since winbindd from 3.0.21b was the only process ever maintaining
this file, wouldn't this still make it a significant bug worth looking
into?
Yes. But the only real solution is to have winbindd remove
the corrupted file automatically and reopen it. It's a robustness
fix.
I agree that this'd be a useful generic change to limit the
*consequences* of any tdb cache file corruption (which winbindd should
still avoid to contribute to in the first place, of course).
Are you saying that we'll see such a change in one of the upcoming
releases (3.0.21c or 3.0.22)?
-TL
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
