Marc-André Lureau be00118d5d util: keep the pidfile locked ... Unfortunately, advisory record locking lose the lock if any fd refering to the file is closed. There doesn't seem to be a way to preserve the lock atomically. We could eventually retake the lock if low pidfilefd is required. This fixes processes being leaked, as they are not killed in virPidFileForceCleanupPath() if the lock can be taken. Here also, we may consider this is not good enough, as a process may leak by simply closing the pidfilefd. Fixes commit d146105f1e ("virCommand: Actually acquire pidfile instead of just writing it") Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>		2020-03-25 09:04:49 +01:00
..
test2.log
test3.log	tests: remove event loop from command test	2020-02-04 14:00:44 +00:00
test4.log	util: keep the pidfile locked	2020-03-25 09:04:49 +01:00
test5.log
test6.log
test7.log
test8.log
test9.log
test10.log
test11.log
test12.log
test13.log
test14.log
test15.log
test16.log
test20.log
test21.log
test26.log
test27.log	tests: remove event loop from command test	2020-02-04 14:00:44 +00:00