From: Andrew Diakin <adiakin@gmail.com>
To: nfs@lists.sourceforge.net
Subject: Trouble with nfs via nfs
Date: Sat, 24 Dec 2005 17:25:30 +0300 [thread overview]
Message-ID: <a97bcc260512240625w60a0b048l@mail.gmail.com> (raw)
Hello, I have a trouble in such thing - on server (server2) I mount
nfs or samba (the result will be same) resource from server1 in /path,
then write in /etc/exports
/path client1(rw) and restart nfs server. Next I mount on client1
mount server2:/path /mnt/path and under /mnt/path I don't see any
files while I cat perfectly see directories. Does anybody know why and
how to change this?
P.S. sorry for my english
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2005-12-24 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-24 14:25 Andrew Diakin [this message]
2005-12-24 15:46 ` Trouble with nfs via nfs Trond Myklebust
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=a97bcc260512240625w60a0b048l@mail.gmail.com \
--to=adiakin@gmail.com \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.