DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 295933858D37
MIME-Version: 1.0
Date: Fri, 1 Sep 2023 06:23:57 +0200
Message-ID: <CALXu0UfRxk5G=3OjbwoNFW7xSj1rHTNw5giS6YZb9p1gF5ceTA@mail.gmail.com>
Subject: Cygwin generates syscalls for *.lnk files on filesystems with native
 symlink support?
To: cygwin AT cygwin DOT com
From: Cedric Blancher via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Cedric Blancher <cedric DOT blancher AT gmail DOT com>
Content-Type: text/plain; charset="utf-8"
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>
Content-Transfer-Encoding: 8bit

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 DOT blancher AT gmail DOT com>
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple