On Fri, Apr 13, 2007 at 02:36:51PM +1000, [EMAIL PROTECTED] wrote:
>
> That wasn't my question. I don't doubt that it is possible to get a
> corrupt tdb file. What I am asking is if you have seen a corrupt tdb
> file that causes a 'wild pointer', and presumably a crash in the tdb
> code that is re
Jeremy,
> The issue some (real) customers are seeing is with laptops
> (mainly I believe) going down hard - no shutdown. In that
> case without the equivalent of an msync it's easy to get
> a corrupted tdb state.
That wasn't my question. I don't doubt that it is possible to get a
corrupt tdb
On Fri, Apr 13, 2007 at 01:41:39PM +1000, [EMAIL PROTECTED] wrote:
>
> Did you really see problems like this with any tdb file? If so, can
> you please send me the tdb file?
No, no winbindd access will produce such a tdb file.
> tdb should be doing range checking on all offsets from the db. If i
> Volker is clever :-). Use TDB_NOMMAP to prevent any wild pointer
> problems when validating the winbindd cache. Wish I'd have
> thought of that.
Did you really see problems like this with any tdb file? If so, can
you please send me the tdb file?
tdb should be doing range checking on all offs
