From: Ken Brown <kbrown@cornell.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: yamaoka@jpl.org, 70415@debbugs.gnu.org
Subject: bug#70415: 30.0.50; [Cygwin] `lock-file' creates a symlink with funny name
Date: Sat, 4 May 2024 13:30:12 -0400 [thread overview]
Message-ID: <c0a50599-7692-43ea-8229-7b318c022e35@cornell.edu> (raw)
In-Reply-To: <fa5ab0b0-3803-4b4c-8ff6-b3aa447473ef@cornell.edu>
On 5/4/2024 1:15 PM, Ken Brown wrote:
> On 5/2/2024 10:26 AM, Ken Brown wrote:
>> On 5/2/2024 2:21 AM, Eli Zaretskii wrote:
>>>> Date: Wed, 1 May 2024 17:20:20 -0400
>>>> Cc: yamaoka@jpl.org, 70415@debbugs.gnu.org
>>>> From: Ken Brown <kbrown@cornell.edu>
>>>>
>>>>> char const *lock_info_fmt = (boot
>>>>> ? "%s@%s.%"PRIdMAX":%"PRIdMAX
>>>>> : "%s@%s.%"PRIdMAX);
>>>>> int len = snprintf (lock_info_str, sizeof lock_info_str,
>>>>> lock_info_fmt, user_name, host_name, pid, boot);
>>>>>
>>>>> get_boot_sec calls get_boot_time, which is a Gnulib function (see
>>>>> lib/boot-time.c). So I guess the key to unlock this puzzle is
>>>>> somewhere there.
>>>>
>>>> I took a quick look at get_boot_time and found a bug, which may explain
>>>> why some Cygwin systems behave differently from others. I've reported
>>>> it here:
>>>>
>>>> https://lists.gnu.org/archive/html/bug-gnulib/2024-05/msg00008.html
>>>
>>> Thanks. This probably explains why the ":-NNNN" part sometimes
>>> appears and sometimes doesn't appear in Cygwin builds of Emacs, but
>>> AFAIU it does NOT explain why unlinking the symlink (when the file is
>>> unlocked) fails when the lock file name includes the ":-NNNN" part.
>>> Right?
>>
>> Yes, that's right. I still need to look into that.
>
> It turns out that there was a Cygwin bug (already fixed in the Cygwin
> development sources) that affected only version 3.5.3, and Bruno added a
> workaround to Gnulib. I now see the ":NNNN" part on my system, without
> a minus sign, and the lock file is deleted properly.
>
> Katsumi, can you apply Bruno's two patches and confirm that the bug is
> fixed?
By the way, you'll have to touch lib/boot-time.c before rebuilding,
because the dependence of the latter on lib/boot-time-aux.h is not
detected by the build system.
Ken
next prev parent reply other threads:[~2024-05-04 17:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 12:33 bug#70415: 30.0.50; [Cygwin] `lock-file' creates a symlink with funny name Katsumi Yamaoka
2024-04-16 13:32 ` Eli Zaretskii
2024-04-16 18:01 ` Pierre Téchoueyres
2024-04-16 22:57 ` Ken Brown
2024-04-17 12:08 ` Eli Zaretskii
2024-04-16 23:58 ` Katsumi Yamaoka
2024-04-17 12:21 ` Eli Zaretskii
2024-04-22 16:15 ` Ken Brown
2024-04-29 23:05 ` Ken Brown
2024-04-30 2:34 ` Eli Zaretskii
2024-04-30 6:45 ` Katsumi Yamaoka
2024-04-30 15:23 ` Ken Brown
2024-04-30 16:20 ` Eli Zaretskii
2024-05-01 21:20 ` Ken Brown
2024-05-02 6:21 ` Eli Zaretskii
2024-05-02 14:26 ` Ken Brown
2024-05-04 17:15 ` Ken Brown
2024-05-04 17:25 ` Eli Zaretskii
2024-05-04 17:46 ` Ken Brown
2024-05-04 22:01 ` Ken Brown
2024-05-05 5:40 ` Eli Zaretskii
2024-05-05 16:21 ` Ken Brown
2024-05-05 16:32 ` Eli Zaretskii
2024-05-05 17:02 ` Ken Brown
2024-05-05 18:00 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-07 0:07 ` Katsumi Yamaoka
2024-05-04 17:30 ` Ken Brown [this message]
2024-05-04 17:37 ` Eli Zaretskii
2024-05-04 18:46 ` Ken Brown
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=c0a50599-7692-43ea-8229-7b318c022e35@cornell.edu \
--to=kbrown@cornell.edu \
--cc=70415@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=yamaoka@jpl.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.