tdbs in cache_dir or state_dir

Stefan Metzmacher metze at
Thu Aug 18 12:07:14 UTC 2016

Hi Christof,

basically lock_path() is for CLEAR_IF_FIRST files,

cache_path() is on persistent storage but can safely deleted
by the admin. And state_path() is for real persistent data.

winbindd_cache.tdb is only in state_path() because of the
"winbind offline logon" option. otherwise is could be
in lock_path() as it's CLEAR_IF_FIRST.


Am 17.08.2016 um 23:58 schrieb Christof Schmitt:
> commit 54529fd354275cfb4ece407f95ef34675b202ea3
> Author: Stefan Metzmacher <metze at>
> Date:   Thu Mar 28 11:00:27 2013 +0100
>     s3:lib/gencache: place gencache.tdb into /var/cache/samba
>     /var/lock/samba is located on tmpfs on newer systems,
>     but we want to keep things like the server affinity cache
>     across reboots.
>     Signed-off-by: Stefan Metzmacher <metze at>
>     Reviewed-by: Volker Lendecke <vl at>
> Shouldn't gencache.tdb placed in the state directory? At least the
> documentation suggests that this is meant for persistent data.
> On the other hand, winbindd_cache.tdb is placed in state_path. Does that
> database hold any data that needs to be kept persistent, or should it be
> moved to cache_path?
> At least my current understanding is that 'lock directory' and 'cache
> directory' could be placed on a tmpfs, while  the important information
> that needs to be kept across reboots is in the 'state directory'.
> Christof

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the samba-technical mailing list