RE: nfs questions!!!
- From: Aaron Konstam <akonstam@xxxxxxxxxxxxx>
- Date: Mon, 31 Jul 2006 15:31:29 -0500
On Mon, 2006-07-31 at 11:43 -0700, bruce wrote:
hi...You must be doing something wrong since we do this all the time. Note:
further research hasn't solved the issue.
i have the server nfs
/etc/exports
/college 192.168.1.*(rw)
i have the client nfs/mount
mount -o rw 192.168.1.52:/college /college
when i add a file to the share as client1, the client and the nfs server can
edit the file with no problem. the other clients can't!! in fact, the file
attributes are changed/set to some very large number...
1, Do oyu mean the owner eis a large number = -2 == nobody. That is a
problem since that will affect accessing the file.
2. You have nfs and nfslock initscripts running on the server.
3. The mounting should be done via a fstab as type nfs.
Maybe posting you exports file and fstab would help.
--
if i go to the nfs server, and i make the changes to the file
(chmod,chgrp,chown) then the settings are somewhat seen by the other
clients, and each client can then edit the given files on the nfs share...
i would have thought that there should be a way to set up the nfs, so that
client1 can create/add a file, and that client2 can edit the file, and vice
versa....
searching via google seems to indicate that this should work, but i can't
see how to get it to perform.
thanks
ps. yeah, there are read/write privs on the nfs mount for the clients
and yeah, the user is the same on each machine
-----Original Message-----
From: Thom Paine [mailto:painethom@xxxxxxxxx]
Sent: Monday, July 31, 2006 10:49 AM
To: bedouglas@xxxxxxxxxxxxx; For users of Fedora Core releases
Subject: Re: nfs questions!!!
Do you have a user with the same name and password on both hosts?
Does said user have write permissions on the directory?
Is this root? Then you need a change to your exports line.
/video 10.10.10.0/24(rw,no_root_squash)
That is the line I use for my mythbox.
--
-=/>Thom
=======================================================================
In my experience, if you have to keep the lavatory door shut by
extending your left leg, it's modern architecture. -- Nancy Banks Smith
=======================================================================
Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@xxxxxxxxxxxxx
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
- References:
- RE: nfs questions!!!
- From: bruce
- RE: nfs questions!!!
- Prev by Date: Re: port blocked on FC4
- Next by Date: Re: Sound on Acer Aspire ZWLMi notebook
- Previous by thread: Re: nfs questions!!!
- Next by thread: iCal Server
- Index(es):
Relevant Pages
- V210 BGE0@1000FDX
... When connecting a server to a Gig interface you need to enable autoneg ... Blocked
port after process kill ... NFS oddity ... where hostname is the name of the
NFS client which will automount the ... (SunManagers) - 2.6.9: NFS (+XFS) Problem - Clients getting Stale filehandles.
... I'm having a rather vierdNFS Problem. ... We have a disk-backup server
... running an NFS server exporting an XFS filesystem to a number of clients ...
Client and server are on the same LAN - no firewall. ... (Linux-Kernel) - Re: Help me replace some Windows installations
... > Possible with untrusted clients in SMB, and trusted clients in NFS. ...
>> trust every client that might be connected to this network. ... > Still, user
ABC on client, accesses to server with rights of the user ... > which Peter already
told you about, or use SMB for Linux to Linux ... (comp.os.linux.setup) - Errors writing large files via NFS
... files larger than a certain size to a NFS server. ... client systems,
although the definition of "too large" varies. ... network paths involved, I'm pretty sure
we're not seeing a network problem. ... (Tru64-UNIX-Managers) - Re: Still getting NFS client locking up
... > the same NFS lockups. ... > Reading from the server works perfectly
all the time. ... > NFS CLIENT: ... in particular, look at traces for
any client blocked in NFS, ... (freebsd-current)