Linux NFS development
 help / color / mirror / Atom feed
From: Eri Mendz <jerimed@myrealbox.com>
To: nfs@lists.sourceforge.net
Subject: NFS dilemma: only one-sided file sharing
Date: Wed, 17 Nov 2004 08:18:26 +0300	[thread overview]
Message-ID: <419ADF22.1000506@myrealbox.com> (raw)

Hello group,

My problem is exactly as stated: NFS is working one-way only. I can put
files in the server and client can access it but readonly. Doing the 
other way around i cannot do, i get permission denied anytime i transfer 
file[s] to the server mount share. Here is my setup:

NFS server:
Slackware 10

# /etc/exports
# 192.168.0.3 is MEPIS box
/nfs    192.168.0.3(rw,anonuid=1000,anongid=100)

# /etc/hosts.allow
portmap :       192.168.0.3
lockd   :       192.168.0.3
mountd  :       192.168.0.3
rquotad :       192.168.0.3
statd   :       192.168.0.3

# /etc/hosts.deny
portmap:ALL
lockd:ALL
mountd:ALL
rquotad:ALL
statd:ALL

NFS client:
MEPIS 2004.01

# /etc/fstab
# nfs entry
alpha:/nfs /mepisNFS nfs hard,rw,rsize=8192,wsize=8192,timeo=14,intr 0 0

My target is to transfer my config files from client to server. Also i 
dont know why the files in server mount share is readonly whereas i set 
it rw in /etc/exports file.

rpcinfo -p of client:

    program vers proto   port
     100000    2   tcp    111  portmapper
     100000    2   udp    111  portmapper
     100021    1   udp  32768  nlockmgr
     100021    3   udp  32768  nlockmgr
     100021    4   udp  32768  nlockmgr
     100021    1   tcp  32768  nlockmgr
     100021    3   tcp  32768  nlockmgr
     100021    4   tcp  32768  nlockmgr
     100024    1   udp    962  status
     100024    1   tcp    965  status

And for the server:

    program vers proto   port
     100000    2   tcp    111  portmapper
     100000    2   udp    111  portmapper
     100011    1   udp    920  rquotad
     100011    2   udp    920  rquotad
     100011    1   tcp    923  rquotad
     100011    2   tcp    923  rquotad
     100003    2   udp   2049  nfs
     100003    3   udp   2049  nfs
     100021    1   udp   1026  nlockmgr
     100021    3   udp   1026  nlockmgr
     100021    4   udp   1026  nlockmgr
     100005    1   udp    932  mountd
     100005    1   tcp    935  mountd
     100005    2   udp    932  mountd
     100005    2   tcp    935  mountd
     100005    3   udp    932  mountd
     100005    3   tcp    935  mountd
     100024    1   udp    938  status
     100024    1   tcp    941  status

I dont know if nfs-utils client-side got something to do with the 
problem for i cant find it in mepis box. This is my first time setting 
up NFS and clueless where to go next. I appreciate any help you good 
people can provide. TIA.

-- 
Regards,
erimendz ** use firefox/thunderbird **
http://www.spreadfirefox.com/?q=affiliates&amp;id=6670&amp;t=58



-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

                 reply	other threads:[~2004-11-17  5:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=419ADF22.1000506@myrealbox.com \
    --to=jerimed@myrealbox.com \
    --cc=erimendz@fastmail.fm \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox