mirror of
https://github.com/samba-team/samba.git
synced 2024-12-24 21:34:56 +03:00
1386200be5
At more than one large site I've seen significant problems due to gencache_stabilize. gencache_stabilize was mainly introduced to survive machine crashes with the cache still being in place. Given that most installations crash rarely and this is still a cache, this safety is overkill and causes real problems. With the recent changes to tdb, we should be safe enough to run on completely corrupted databases and properly detect errors. A further commit will introduce code that wipes the gencache.tdb if such a corruption is detected. There is one kind of corruption that we don't properly handle: Orphaned space in the database. I don't have a good idea yet how to handle this in a graceful and efficient way during normal operations, but maybe this idea pops up at some point. Signed-off-by: Volker Lendecke <vl@samba.org> Reviewed-by: Jeremy Allison <jra@samba.org> |
||
---|---|---|
.. | ||
asyncdns.c | ||
nmbd_become_dmb.c | ||
nmbd_become_lmb.c | ||
nmbd_browserdb.c | ||
nmbd_browsesync.c | ||
nmbd_elections.c | ||
nmbd_incomingdgrams.c | ||
nmbd_incomingrequests.c | ||
nmbd_lmhosts.c | ||
nmbd_logonnames.c | ||
nmbd_mynames.c | ||
nmbd_namelistdb.c | ||
nmbd_namequery.c | ||
nmbd_nameregister.c | ||
nmbd_namerelease.c | ||
nmbd_nodestatus.c | ||
nmbd_packets.c | ||
nmbd_processlogon.c | ||
nmbd_proto.h | ||
nmbd_responserecordsdb.c | ||
nmbd_sendannounce.c | ||
nmbd_serverlistdb.c | ||
nmbd_subnetdb.c | ||
nmbd_synclists.c | ||
nmbd_winsproxy.c | ||
nmbd_winsserver.c | ||
nmbd_workgroupdb.c | ||
nmbd.c | ||
nmbd.h | ||
wscript_build |