mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-23 21:34:54 +03:00
be00118d5d
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>
16 lines
184 B
Plaintext
16 lines
184 B
Plaintext
ENV:DISPLAY=:0.0
|
|
ENV:HOME=/home/test
|
|
ENV:HOSTNAME=test
|
|
ENV:LANG=C
|
|
ENV:LOGNAME=test
|
|
ENV:PATH=/usr/bin:/bin
|
|
ENV:TMPDIR=/tmp
|
|
ENV:USER=test
|
|
FD:0
|
|
FD:1
|
|
FD:2
|
|
FD:5
|
|
DAEMON:yes
|
|
CWD:/
|
|
UMASK:0022
|