From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
To: Ryan Winter <ryan.winter@nautronix.com.au>, cygwin@cygwin.com
Subject: Re: inetd and microsoft nfs
Date: Sun, 11 Nov 2001 08:26:00 -0000 [thread overview]
Message-ID: <4.3.1.2.20011112195144.022223f8@pop.ma.ultranet.com> (raw)
Message-ID: <20011111082600.E3IYziZnLGMDERAnMsl_HXeT8PTYW1TOgh0n_p6MUkw@z> (raw)
In-Reply-To: <1005612061.30434.15.camel@alice>
At 07:41 PM 11/12/2001, Ryan Winter wrote:
>Just wanted to know if anyone else has used this combination of
>software.
>
>When I access nfs mounted drives (using microsoft nfs) with the inetd
>the symlinks magically disappear (they dont appear with ls and I can
>change into that directory either). When I view the directory locally
>with cygwin (or explorer), there is no problem with the symlinks.
>
>My question is: Exactly how does the inetd work that it could cause this
>effect. The only though I have is that the inetd is somehow changing the
>login state which is effecting the nfs mount.
I expect your problem is similar to the following FAQ entry.
Why don't symlinks work on samba-mounted filesystems?
http://www.cygwin.com/faq/faq_4.html#SEC65
Obviously, the solution is not exactly the same. My guess is your NFS
software is the component at fault but you'd need to debug this
situation to be sure. Why not use UNC/drive mappings for Windows machines
or Samba for other machines? That's one solution that doesn't require
any debugging! ;-)
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
838 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next parent reply other threads:[~2001-11-13 1:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1005612061.30434.15.camel@alice>
2001-11-01 18:23 ` Larry Hall (RFK Partners, Inc) [this message]
2001-11-11 8:26 ` Larry Hall (RFK Partners, Inc)
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=4.3.1.2.20011112195144.022223f8@pop.ma.ultranet.com \
--to=lhall@rfk.com \
--cc=cygwin@cygwin.com \
--cc=ryan.winter@nautronix.com.au \
/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).