search for: offline_tdb_copi

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

On 2019-11-13 13:11, Andrea Venturoli wrote: > I'm open to suggestions... Some further step... It's samba-tool itself that locks the file before calling tdbbackup. Running "samba-tool domain backup offline ..." spawns "tdbbackup -s .copy.tdb /var/db/samba4/private/secrets.ldb -r", which gets stuck. Running "tdbbackup -s .copy.tdb

On Thu, 2019-11-21 at 14:58 +0100, Andrea Venturoli wrote: > On 2019-11-13 13:11, Andrea Venturoli wrote: > > > I'm open to suggestions... > > Some further step... > > It's samba-tool itself that locks the file before calling tdbbackup. > > Running "samba-tool domain backup offline ..." spawns "tdbbackup -s > .copy.tdb

On Thu, July 23, 2020 15:56, Andrew Bartlett wrote: > > Clearly there is, as otherwise we could not be in waitpid on it. > The process is not a python process, it will be tdbbackup. The > command line arguments to that process will be instructive. Here it is: root 36800 0.8 0.0 12556 2788 1 SJ 16:49 0:00.01 /usr/local/bin/tdbbackup -s .copy.tdb