Re: [Sheflug] Networking

[Craig Andrews <nospam [at] xxxxxxxxxxxxxx>]

On Thu, 2003-01-09 at 09:51, Alec Melling wrote:
> Suse 8.1 in Yast gives you the options of either nfs server or client. I have 
> the server on one manchine and the client on another. I am affraid that I 
> don't understand the term nfsd?

You need a server and client at each end. nfsd is the server daemon

> File transfer is ok server to client, but not client to server!

?? This can't be right. The machine which mounts a remotely shared
directory is the client. This can then read and write to/from the
server. It is not possible for the server to write to the client.

> I did consider wheter or not I should set-up both machines as server/clients, 
> but this seemed illogical, the client not being able to write to the server?

The client can write to the server, it is the server that cannot write
to the clients. This is in fact perfectly logical (to some of us :)  

Time for an example, I think. Not doing well today. Say you have 2
machines, A and B. A wants to mount /home on B, and B wants to mount
/usr/local on A (don't ask why, it's hypothetical). Therefore, A needs
to run an NFS server to export /usr/local, and mount, as a client, /home
on B. B needs to run an NFS server to export /home, and mount, as a
client, /usr/local on A.

Clear as mud? 

Just an aside, a connection where each machine can write to the other is
a peer-peer relationship, not client-server. Essentially, a peer-peer
relationship is a case where each machine is acting as both client and
server. NFS is a client-server relationship, so two links have to exist
for mutual file sharing.

-- 
Craig Andrews
craig@fishbot.org.uk


___________________________________________________________________

Sheffield Linux User's Group -
http://www.sheflug.co.uk/mailfaq.html

  GNU the choice of a complete generation.