From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: too many level of symbolic links
Date: Thu, 17 Feb 2022 13:00:20 +0100 [thread overview]
Message-ID: <Yg441DvDsCdNP1Bn@calimero.vinschen.de> (raw)
In-Reply-To: <002a01d823ea$e6bdafa0$b4390ee0$@uni-bremen.de>
On Feb 17 11:41, Andreas Heckel wrote:
>
>
> > Of Oskar Skog
> > Sent: Thursday, February 17, 2022 11:05 AM
> > Subject: Re: too many level of symbolic links
> >
> > On 2022-02-17 10:46, Andreas Heckel wrote:
> > > I have a network drive mapped like
> > > //hostname/share --> p:
> > >
> > > When trying to access the network drive via cygwin I get:
> > >
> > > $ ls /cygdrive/p
> > > ls: cannot open directory '/cygdrive/p': Too many levels of symbolic
> > links
> > >
> > > Accessing the network share directly via //hostname/share works as
> > normal.
> > >
> > > I have been using cygwin a long time but this is the first time this
> > happens. My machine and our servers got recently updated, so I can't
> > really pinpoint the reason for this behaviour now.
> > >
> > > Any hints / advice how to resolve this?
> > >
> > > Cheers, Andreas
> > >
> > >
> >
> >
> >
> > Are you running the newest version of Cygwin (3.3.4)?, there have been
> > a similar issue to yours in the previous version that should have been
> > fixed.
> >
>
> Just to be certain, I ran setup again. There are currently no pending updates.
>
> 3472k 2022/01/31 C:\cygwin64\bin\cygwin1.dll
> Cygwin DLL version info:
> DLL version: 3.3.4
There was YA patch necessary to fix this regression
https://sourceware.org/git/?p=newlib-cygwin.git;a=commitdiff;h=71d5490a3a2d
and that patch isn't in 3.3.4. Please test the latest (2022-02-17)
Cygwin snapshot DLL from https://cygwin.com/snapshots/
Thanks,
Corinna
next prev parent reply other threads:[~2022-02-17 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 8:46 Andreas Heckel
2022-02-17 10:05 ` Oskar Skog
2022-02-17 10:41 ` Andreas Heckel
2022-02-17 12:00 ` Corinna Vinschen [this message]
2022-02-17 12:41 ` Andreas Heckel
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=Yg441DvDsCdNP1Bn@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).