From: Bernhard Bitsch <bbitsch@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Stale pakfire lock-file causing pakfire to no longer work
Date: Thu, 15 Sep 2022 13:48:42 +0200 [thread overview]
Message-ID: <5d1bd063-7a35-03ff-42c6-5af63a5ac0fb@ipfire.org> (raw)
In-Reply-To: <f65f8c8ebced8570c7ee30c1a9eaa285b71b3894.camel@sicho.home>
[-- Attachment #1: Type: text/plain, Size: 372 bytes --]
Hi all,
as an 'old real time programmer' this reminds me deeply at
Dijkstra/Hoare's "Dining philosophers problem".
The check for presence of the lockfile and the generation of it are not
'atomic'. Means two programs can run in parallel.
I'll investigate this further. But the deletion of the lock should
happen anyways, as far I've seen till now.
Regards,
Bernhard
next prev parent reply other threads:[~2022-09-15 11:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 19:48 Robin Roevens
2022-09-15 7:39 ` Peter Müller
2022-09-15 19:01 ` Robin Roevens
2022-09-15 19:09 ` Bernhard Bitsch
2022-09-15 11:48 ` Bernhard Bitsch [this message]
2022-09-15 19:43 ` Robin Roevens
2022-09-15 20:03 ` Bernhard Bitsch
2022-09-15 20:30 ` Robin Roevens
2022-09-15 23:27 ` Bernhard Bitsch
2022-09-17 21:56 ` Robin Roevens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5d1bd063-7a35-03ff-42c6-5af63a5ac0fb@ipfire.org \
--to=bbitsch@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox