Recently, I have encountered similar problems in my CentOS 7 environment.
`[root@controller-3 ~]# uname -a
Linux controller-3 3.10.0-862.el7.x86_64 #1 SMP Fri Apr 20 16:44:24 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
[root@controller-3 ~]# cat /etc/redhat-release
CentOS Linux release 7.5.1804
@jaymzh Yes, the processes running as root account.
`the memmap() the DB read-write, and write it back out when they are done...
hence if then something changes at the same time, one of those process can
write back old pages.`
`# ls -lthra /var/lib/rpm
total 70M
-rw-r--r--. 1 root root0
Can not avoid it?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/232#issuecomment-557374397___
Rpm-maint mailing list
In the process of testing dcrpm, when I execute the command line lsof - F p
/var/lib/rpm/.dbenv.lock, lsof displays the PIDs of all processes, including 1,
instead of only displaying the PIDs of the .dbenv.lock file;
It may have been generated after I installed typing (Python module)
@jaymzh I see that dcrpm used typing(begin python-3.5 as a new feature added)
, but my project is running on centos 7.5 1804 and using the python 2.7.5
version, Is typing(dcrpm) compatible with Python 2.7.5?
--
You are receiving this because you are subscribed to this thread.
Reply to this
