GNU bug report logs - #49261
28.0.50; File Locking Breaks Presumptuous Toolchains

Previous Next

Full log

Message #11 received at 49261 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: ncaprisunfan <at> gmail.com, 49261 <at> debbugs.gnu.org
Subject: Re: bug#49261: 28.0.50; File Locking Breaks Presumptuous Toolchains
Date: Wed, 30 Jun 2021 16:26:22 +0300

> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Date: Wed, 30 Jun 2021 15:00:41 +0200
> Cc: 49261 <at> debbugs.gnu.org
> 
> Would it make sense to allow the user to control where the lockfiles are
> written?

Yes, I think so.  But it is not as trivial as it could sound,
because...

> The lockfiles are symlinks, so it should theoretically be
> possible to have them elsewhere without being any racier than the code
> currently is, I think.

...even if the lock files are symlinks (which they not necessarily
are), we need to handle the case of several files with identical
basenames in different directories.  (Their being symlinks is
unimportant, because the target of the symlink doesn't exist.)

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.