Hi Jan Korbel,
On Thu, Feb 09, 2012 at 11:36:38AM +0100, Jan Korbel wrote:
> Package: apticron
> Version: 1.1.42
>
> apticron in Squeeze runs automatically by:
>
> * /etc/cron.daily/apticron in 6:25
> * /etc/cron.d/apticron in random time generated by postinst script
>
> We had one installation with random generated time 6:25. Because of
> this there was a collision of two apticron processes:
>
> /etc/cron.daily/apticron:
> E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource
> temporarily unavailable)
> E: Unable to lock directory /var/lib/apt/lists/
>
> I think /etc/cron.daily/apticron is not necessary because of
> duplicity. Furthermore there are peaks on Debian servers and client
> connection in one moment.
>
> At least there should be a condition to not generate 6:25.
Thanks for reporting. Please see the following changelog entries and tell me if
theses changes help. I'll try to find some time to push a squeeze backport
soon, but you could start using the updated version from testing, which seems
quite stable.
apticron (1.1.47) unstable; urgency=low
[ patches by Gian Piero Carrubba ]
* Run every hour via cron.d snippet just exiting if fully executed in the
past 24h. (Closes: #587597)
* Reword the '--cron' parameter help message.
* Move the timestamp file to /var/lib/apticron as it now exists.
* cron.d snippet: cleanly exit if apticron has been removed.
* Supposedly trap all errors when parsing existent cron.d snippet.
[...]
apticron (1.1.43) unstable; urgency=low
* Remove deprecated cron.daily file. Thanks to Piotr Lewandowski.
(Closes: #587597)
Regards,
--
--------------------------------------------------------------------------------
.''`. Tiago Bortoletto Vaz GPG : 1024D/A504FECA
: :' : http://tiagovaz.org XMPP : tiago at jabber.org
`. `' tiago at {tiagovaz,debian}.org IRC : tiago at OFTC
`- Debian GNU/Linux - The Universal OS http://www.debian.org
--------------------------------------------------------------------------------
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]