From: Cedric Blancher <cedric.blancher@gmail.com>
To: cygwin@cygwin.com
Subject: Cygwin generates syscalls for *.lnk files on filesystems with native symlink support?
Date: Fri, 1 Sep 2023 06:23:57 +0200 [thread overview]
Message-ID: <CALXu0UfRxk5G=3OjbwoNFW7xSj1rHTNw5giS6YZb9p1gF5ceTA@mail.gmail.com> (raw)
Good morning!
During a Cygwin 3.4.8-1.x86_64 debugging session I noticed something
odd when I looked at the network traffic generated by one of our
cluster nodes:
It seems that for each call to a tool (i.e. starting "sed" from
"bash") Cygwin searches for *.lnk files.
Is this correct even when the filesystem in question has native
symlink support (e.g. NFS)?
Excerpt from tshark:
1746 3.800878384 192.168.2.152 → 192.168.2.150 NFS 298 V4 Call lookup
LOOKUP DH: 0x49b89d4e/staden | LOOKUP sed
1747 3.800910202 192.168.2.150 → 192.168.2.152 NFS 318 V4 Reply (Call
In 1746) lookup LOOKUP | LOOKUP Status: NFS4ERR_NOENT
1748 3.801293956 192.168.2.152 → 192.168.2.150 NFS 266 V4 Call lookup
LOOKUP DH: 0x2cf62c0d/sed.exe
1749 3.801319051 192.168.2.150 → 192.168.2.152 NFS 162 V4 Reply (Call
In 1748) lookup LOOKUP Status: NFS4ERR_NOENT
1750 3.801636441 192.168.2.152 → 192.168.2.150 NFS 266 V4 Call lookup
LOOKUP DH: 0x2cf62c0d/sed.lnk
1751 3.801659474 192.168.2.150 → 192.168.2.152 NFS 162 V4 Reply (Call
In 1750) lookup LOOKUP Status: NFS4ERR_NOENT
1752 3.801981533 192.168.2.152 → 192.168.2.150 NFS 270 V4 Call lookup
LOOKUP DH: 0x2cf62c0d/sed.exe.lnk
1753 3.802003824 192.168.2.150 → 192.168.2.152 NFS 162 V4 Reply (Call
In 1752) lookup LOOKUP Status: NFS4ERR_NOENT
1754 3.810270585 192.168.2.152 → 192.168.2.150 NFS 266 V4 Call lookup
LOOKUP DH: 0x2cf62c0d/sed.bat
1755 3.810345438 192.168.2.150 → 192.168.2.152 NFS 162 V4 Reply (Call
In 1754) lookup LOOKUP Status: NFS4ERR_NOENT
1756 3.810768112 192.168.2.152 → 192.168.2.150 NFS 270 V4 Call lookup
LOOKUP DH: 0x2cf62c0d/sed.bat.exe
1757 3.810795216 192.168.2.150 → 192.168.2.152 NFS 162 V4 Reply (Call
In 1756) lookup LOOKUP Status: NFS4ERR_NOENT
1758 3.811234114 192.168.2.152 → 192.168.2.150 NFS 270 V4 Call lookup
LOOKUP DH: 0x2cf62c0d/sed.bat.lnk
1759 3.811254882 192.168.2.150 → 192.168.2.152 NFS 162 V4 Reply (Call
In 1758) lookup LOOKUP Status: NFS4ERR_NOENT
1760 3.811728762 192.168.2.152 → 192.168.2.150 NFS 274 V4 Call lookup
LOOKUP DH: 0x2cf62c0d/sed.bat.exe.lnk
1761 3.811802518 192.168.2.150 → 192.168.2.152 NFS 162 V4 Reply (Call
In 1760) lookup LOOKUP Status: NFS4ERR_NOENT
1762 3.820028572 192.168.2.152 → 192.168.2.150 NFS 266 V4 Call lookup
LOOKUP DH: 0x2cf62c0d/sed.sh
1763 3.820128384 192.168.2.150 → 192.168.2.152 NFS 162 V4 Reply (Call
In 1762) lookup LOOKUP Status: NFS4ERR_NOENT
1764 3.820495809 192.168.2.152 → 192.168.2.150 NFS 270 V4 Call lookup
LOOKUP DH: 0x2cf62c0d/sed.sh.exe
1765 3.820560543 192.168.2.150 → 192.168.2.152 NFS 162 V4 Reply (Call
In 1764) lookup LOOKUP Status: NFS4ERR_NOENT
1766 3.821000559 192.168.2.152 → 192.168.2.150 NFS 270 V4 Call lookup
LOOKUP DH: 0x2cf62c0d/sed.sh.lnk
1767 3.821071034 192.168.2.150 → 192.168.2.152 NFS 162 V4 Reply (Call
In 1766) lookup LOOKUP Status: NFS4ERR_NOENT
1768 3.821519236 192.168.2.152 → 192.168.2.150 NFS 274 V4 Call lookup
LOOKUP DH: 0x2cf62c0d/sed.sh.exe.lnk
Also, searching for sed.sh.exe.lnk looks weird. Bug, or feature?
Ced
--
Cedric Blancher <cedric.blancher@gmail.com>
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur
next reply other threads:[~2023-09-01 4:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 4:23 Cedric Blancher [this message]
2023-09-01 10:57 ` Corinna Vinschen
2023-09-26 5:12 ` Cedric Blancher
2023-12-18 12:04 ` Cedric Blancher
2024-01-08 13:56 ` Corinna Vinschen
2024-01-08 17:11 ` matthew patton
2024-01-08 18:11 ` Corinna Vinschen
2024-01-08 18:44 ` matthew patton
2024-01-08 19:05 ` Rainer Emrich
2024-01-08 19:17 ` Jeffrey Altman
2024-01-08 19:21 ` Corinna Vinschen
2024-01-08 19:57 ` matthew patton
2024-01-08 20:27 ` Brian Inglis
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='CALXu0UfRxk5G=3OjbwoNFW7xSj1rHTNw5giS6YZb9p1gF5ceTA@mail.gmail.com' \
--to=cedric.blancher@gmail.com \
--cc=cygwin@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).