Daniel Burrows <dburr...@debian.org> wrote: > /var/lib/apt/lists/lock is an fcntl lockfile, not a dotlock-style > lockfile. i.e., its mere existence isn't enough for the lock to be > held; a currently running process has to be holding the lock. Removing > the lockfile doesn't remove the lock; instead, it causes a second lock > to be created and locked separately (so whatever wanted exclusive > access no longer has it). > > You can track down who's holding the lock next time this happens. The > program "fuser" from psmisc can tell you which PID has the file locked, > and "ps uax | grep <pid>" will usually produce the name of the culprit.
It's apt-get update as invoked by /etc/cron.daily/apt. >From a quick browse of the script, there's an option to turn it off, although it doesn't seem to be running to completion either, which is where the real problem lies. If there is a bug, I have reported it against the wrong package. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
