Hello, Thanks for reviving this, it'll definitely be useful!
Svante Signell, le Thu 08 Jan 2015 12:28:05 +0100, a écrit : > 1) l_pid of struct flock is not set. According to the manpage (and > posix) the PID of the process blocking the lock should be reported. Can > maybe be solved by a shared memory solution in glibc or as indicated in > task 1022. We can not trust a shared memory solution, we need an io_reidentify round through the proc server. > 2) fork(2) does not create a process without the locks set for the > child. > (This is probably the main cause tdbtorture in tdb does not work well > with the current file record locking patches.) I don't think tdbtorture forks with locks held: AIUI it just starts several processes and let them play at will with locks, without creating or terminating them. Samuel
