search for: transaction_cancel

On 2019-11-13 09:30, Andrew Bartlett wrote: > Regarding your problem, on linux I use lslocks to debug from here, you > can normally work out which process is holding the lock, which lock it > is waiting on (if any, marked with a *) and gdb that to work out what > is the matter with it, and perhaps why it is in that situation. Hmm... I have no lslocks on FreeBSD; will lsof do? In

...#39;.ldb', lp=lp) > logger.info('Starting transaction on ' + secrets_path) > secrets_obj.transaction_start() > self.offline_tdb_copy(secrets_path + '.ldb') > self.offline_tdb_copy(secrets_path + '.tdb') > secrets_obj.transaction_cancel() Could the problem be here? I'm not attempting to alter this, before understanding it fully, though. bye & Thanks av.

...; > logger.info('Starting transaction on ' + secrets_path) > > secrets_obj.transaction_start() > > self.offline_tdb_copy(secrets_path + '.ldb') > > self.offline_tdb_copy(secrets_path + '.tdb') > > secrets_obj.transaction_cancel() > > Could the problem be here? > I'm not attempting to alter this, before understanding it fully, though. Is tdbbackup the one provided by the Samba build, or an earlier (system) version? We had to change the lock behaviour in tdb to make this work, if you ran an older version it...

Hi all, As per Jelmer's request - in response to bug #7455 attached diff file. Please let me know what you think and if any modificationes need to be performed Regards Luk -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: newusergroupadv.diff URL: