Bug#1052053: popularity-contest: race condition between the two cron jobs

[Alexandre Detiste <alexandre.detiste@gmail.com>]

Hi,

I realized no other one than me could have realisticaly triggered this
bug in reality...

My test system was a bit hosed which some tests
for upstream systemd-cron development going on.

Still it's a good practice to have locking in cronjobs.

Such feature one gets for free using systemd timers...
(which lead us back to the other bug)
or there should be some canonical way to do it in bash

You might want to close this one bug

Le mar. 2 juil. 2024 à 15:01, Bill Allombert <ballombe@debian.org> a écrit :
> On Sat, Sep 16, 2023 at 06:21:56PM +0200, Alexandre Detiste wrote:
> > Package: popularity-contest
> > Version: 1.77
> > Severity: normal
> >
> > I have been unlucky and the two instance of the cronjob
> > triggered at the same time, stepping on eachother feets.
> >
> > (at the "savelog -c 7 popularity-contest >/dev/null" step precisely)
>
> Sorry for the delay in getting back to you.
>
> > Can you implement some locking ?
>
> I expected savelog would implement locking against itself at least
> but this is not the case.