public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: Philippe Debanne <p.debanne@polymtl.ca>
Subject: Re: Too many level of symbolic links (still have problem with sbmfs network drives)
Date: Tue, 8 Mar 2022 00:14:55 +0900	[thread overview]
Message-ID: <20220308001455.9da9b8e10b76e9350c22520a@nifty.ne.jp> (raw)
In-Reply-To: <20220305112326.8d07e89f03eb382f58023055@nifty.ne.jp>

On Sat, 5 Mar 2022 11:23:26 +0900
Takashi Yano wrote:
> On Fri, 4 Mar 2022 15:43:55 -0500
> Philippe Debanne wrote:
> > Hello Cygwin list,
> > 
> > Since updating my Cygwin installation to the latest version, I am having 
> > the problem of  "Too many levels of symbolic links" on certain network 
> > drives, that was reported in other threads.  I tried replacing the  
> > 'cygwin1.dll' with the snapshots from 2022-02-17 and 2022-03-01 
> > (x86_64).  This did fix the link to one of the network drives, but not 
> > others.
> > 
> > The mount command in my case gives :
> > 
> > $ mount
> > D:/cygwin64/bin on /usr/bin type ntfs (binary,auto)
> > D:/cygwin64/lib on /usr/lib type ntfs (binary,auto)
> > D:/cygwin64 on / type ntfs (binary,auto)
> > C: on /cygdrive/c type ntfs (binary,posix=0,user,noumount,auto)
> > D: on /cygdrive/d type ntfs (binary,posix=0,user,noumount,auto)
> > L: on /cygdrive/l type cifs (binary,posix=0,user,noumount,auto)
> > V: on /cygdrive/v type smbfs (binary,posix=0,user,noumount,auto)
> > W: on /cygdrive/w type smbfs (binary,posix=0,user,noumount,auto)
> > X: on /cygdrive/x type smbfs (binary,posix=0,user,noumount,auto)
> > Y: on /cygdrive/y type smbfs (binary,posix=0,user,noumount,auto)
> > Z: on /cygdrive/z type smbfs (binary,posix=0,user,noumount,auto)
> > 
> > No problem with the local drives, and I can now go to the X: drive 
> > thanks to the recent snapshot.  But not other 'smbfs' ones :
> > 
> > $ cd Z:
> > -bash: cd: Z:: Too many levels of symbolic links
> > 
> > Any ideas what could be wrong ?  It seems to be limited to certain SAMBA 
> > shared drives.
> 
> Hmm, could you please provide the version of samba
> and hopefully smb.conf file if possible?

I cannot reproduce your problem, so more information
is required.

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

  reply	other threads:[~2022-03-07 15:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-04 20:43 Philippe Debanne
2022-03-05  2:23 ` Takashi Yano
2022-03-07 15:14   ` Takashi Yano [this message]
2022-03-07 15:32     ` Philippe Debanne
2022-03-08 23:52       ` Takashi Yano
2022-03-09  0:16         ` Philippe Debanne
2022-03-09  0:58           ` Takashi Yano
2022-03-11  9:09             ` Takashi Yano
2022-03-12  2:36               ` Takashi Yano
2022-03-14  9:49                 ` Corinna Vinschen

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=20220308001455.9da9b8e10b76e9350c22520a@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --cc=cygwin@cygwin.com \
    --cc=p.debanne@polymtl.ca \
    /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).