We've got a machine that is running yum from cron, and currently has
something like 12 instances of yum running. It looks like an rpm lock
issues for a new yum process I start:
stat64("/var/lib/rpm/__db.001", {st_mode=S_IFREG|0644, st_size=16384, ...}) = 0
open("/var/lib/rpm/__db.001", O_RDWR|O_LARGEFILE) = 3
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
fstat64(3, {st_mode=S_IFREG|0644, st_size=16384, ...}) = 0
close(3) = 0
open("/var/lib/rpm/__db.001", O_RDWR|O_LARGEFILE) = 3
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
mmap2(NULL, 16384, PROT_READ|PROT_WRITE, MAP_SHARED, 3, 0) = 0xb73b2000
close(3) = 0
futex(0xb73b2000, FUTEX_WAIT, 2, NULL) = -1 EINTR (Interrupted system call)
--- SIGINT (Interrupt) @ 0 (0) ---
rt_sigreturn(0xb73b2000) = -1 EINTR (Interrupted system call)
futex(0xb73b2000, FUTEX_WAIT, 2, NULL) = -1 EINTR (Interrupted system call)
--- SIGINT (Interrupt) @ 0 (0) ---
rt_sigreturn(0xb73b2000) = -1 EINTR (Interrupted system call)
futex(0xb73b2000, FUTEX_WAIT, 2, NULL) = -1 EINTR (Interrupted system call)
--- SIGINT (Interrupt) @ 0 (0) ---
rt_sigreturn(0xb73b2000) = -1 EINTR (Interrupted system call)
....etc....
Isn't yum's own /var/run/yum.pid lockfile supposed to keep yum from
running but once? If so, shouldn't yum check this file *first* before
trying for a lock on /var/lib/rpm/__db.001 ?? This is disturbing.
--
Joshua Jensen
joshua@xxxxxxxx
"If God didn't want us to eat animals, why did he make them out of meat?"
