mirror of
https://github.com/samba-team/samba.git
synced 2024-12-24 21:34:56 +03:00
7535359602
This will show a leases.tdb record leak. If you SIGSTOP the smbtorture process while it's in the 10-second wait, you will find locking.tdb and share_entries.tdb empty after the scavenger has cleaned up. But there will be an entry in leases.tdb left. I have no clue how to test this properly, or how to have a reasonably cheap assert in smbd during normal operations. The problem is that this leak can't really be distinguished from a "normal" leak that a crashed smbd would leave behind. Possibly we need a background job walking leases.tdb to clean this up properly. Signed-off-by: Volker Lendecke <vl@samba.org> Reviewed-by: Jeremy Allison <jra@samba.org>
3 lines
110 B
Plaintext
3 lines
110 B
Plaintext
# In the ad_dc env leases are disabled
|
|
^samba3.smb2.durable-v2-delay.durable_v2_reconnect_delay_msec\(ad_dc\)
|