On 7 September 2010 15:16, James Hogarth wrote:
> Hi all,
>
> I have a Centos server exporting a filesystem via NFSv4 and from my
> Ubuntu desktop I can mount it specifying the nfs version as 4 fine and
> read/write data.
>
> From another Centos system trying to mount this exported filesystem
> re
Hi all,
I have a Centos server exporting a filesystem via NFSv4 and from my
Ubuntu desktop I can mount it specifying the nfs version as 4 fine and
read/write data.
>From another Centos system trying to mount this exported filesystem
results in "mount.nfs4: Cannot allocate memory" every time.
Bee
> I have nfs version 4 running on a CentOS 5.2 server to export /home.
> That works great so for, but clients can mount /home with nfs version 3
> too. How can I disable nfs v3 on the server?
Check out /etc/sysconfig/nfs .. make your changes and restart nfs
Hello,
I have nfs version 4 running on a CentOS 5.2 server to export /home.
That works great so for, but clients can mount /home with nfs version 3
too. How can I disable nfs v3 on the server?
Thank you
Olaf
___
CentOS mailing list
CentOS@centos.org
h
On Wed, July 23, 2008 14:17, MJT wrote:
> On Wednesday 23 July 2008 9:55:57 am David Dyer-Bennet wrote:
>> > change which versions of NFS get mounted. I haven't had to change
>> > anything else in that file.
>>
>> I don't believe SECURE_NFS does anything; at least, it's not mentioned
>> in
>> /etc
On Wed, July 23, 2008 14:03, Jens Larsson wrote:
>> Well, I definitely understand a couple of things better than when we
>> started. Thank you very much!
>>
>> It is not, however, working. Is that likely to be the "domain="
>> setting,
>> given what I said above?
>
> The "domain" in NFSv4-speak
On Wednesday 23 July 2008 9:55:57 am David Dyer-Bennet wrote:
> > change which versions of NFS get mounted. I haven't had to change
> > anything else in that file.
>
> I don't believe SECURE_NFS does anything; at least, it's not mentioned in
> /etc/init.d/nfs anywhere, and it's not in the nfsd man
> Well, I definitely understand a couple of things better than when we
> started. Thank you very much!
>
> It is not, however, working. Is that likely to be the "domain=" setting,
> given what I said above?
The "domain" in NFSv4-speak has nothing to do with DNS. It _can_ be you
DNS-domainname
On Tue, July 22, 2008 18:39, MJT wrote:
> Ok, I don't have the origional post in my email so I am replying via a
> reply
> cutting and pasting from the archives list web page.
Thank you!
>> Looks like just starting the nfs service turns on V2, 3, and 4 (based on
> reading the script, reading the
Ok, I don't have the origional post in my email so I am replying via a reply
cutting and pasting from the archives list web page.
> Looks like just starting the nfs service turns on V2, 3, and 4 (based on
reading the script, reading the man pages, and looking at the ports using
netstat -l).
That
David Dyer-Bennet wrote:
> I'm not sure I especially care about NFS V4 (this is to share the
> programmers' home directories, so it's easy to work on any of the
> production systems; it won't be particularly high-load or any particularly
> strange usage pattern), but I care about understanding thi
Looks like just starting the nfs service turns on V2, 3, and 4 (based on
reading the script, reading the man pages, and looking at the ports using
netstat -l).
However, I can connect using -t nfs in the mount, and -t nfs4 fails.
I don't believe this is a firewall issue, internal IPs are fully ope
12 matches
Mail list logo
