Re: aptitude löscht lockfile /var/lib/dpkg/lock nicht

[Friedrich Strohmaier <gmane@bits-fritz.de>]

Hi Elimar, *,

Am 21.02.2015 um 16:51 schrieb Elimar Riesebieter:
> * Friedrich Strohmaier <gmane@bits-fritz.de> [2015-02-21 15:51 +0100]:

> [...]
>> Wäre nicht weiter schlimm, wenn nicht cron-apt daran stören würde:

>> Meldung der cron-apt Mail:
>> ========================
>> CRON-APT RUN [/etc/cron-apt/config]: Sat Feb 21 04:00:01 CET 2015
>> CRON-APT SLEEP: 117, Sat Feb 21 04:01:58 CET 2015
>> CRON-APT ACTION: 3-download
>> CRON-APT LINE: /usr/bin/aptitude dist-upgrade -d -y -o APT::Get::Show-Upgraded=true
>> Reading package lists...
>> Building dependency tree...
>> Reading state information...
>> Reading extended state information...
>> Initializing package states...
>> Reading task descriptions...
>> No packages will be installed, upgraded, or removed.
>> 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>> Need to get 0 B of archives. After unpacking 0 B will be used.
>> A package failed to install.  Trying to recover:
>> dpkg: status database area is locked by another process

> Was sagt:
> $ ps aux | egrep (apt|dpkg)

~# ps aux | egrep (apt|dpkg)
-bash: Syntaxfehler beim unerwarteten Wort `apt'

;o))

aber
~# ps aux | grep apt | grep -v grep
~# ps aux | grep dpkg | grep -v grep
~#

und

~# ls -l /var/lib/dpkg/lock
-rw-r----- 1 root root 0 21. Feb 20:40 /var/lib/dpkg/lock

Es wird noch besser:
cron-apt ist 20:40 drübergelaufen, hat den lockfile
geändert und sich dennoch beschwert.

Was schmeckt dem cron-apt nicht??

Friedrich