SCIENTIFIC-LINUX-USERS Archives

September 2008

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Eve V. E. Kovacs" <[log in to unmask]>
Reply To:
Eve V. E. Kovacs
Date:
Fri, 19 Sep 2008 17:01:41 -0500
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (42 lines)
Hi Everyone,
Thanks. I had several people suggest the modprobe.conf fix. I tried it and 
it worked. /etc/sysconfig nfs worked for fixing the mountd, rquotad and 
statd ports, but not the lockd ones.
Eve


On Fri, 19 Sep 2008, Shane Voss wrote:

> Date: Fri, 19 Sep 2008 09:35:22 +0100
> From: Shane Voss <[log in to unmask]>
> To: Dr Andrew C Aitchison <[log in to unmask]>
> Cc: Eve V. E. Kovacs <[log in to unmask]>, [log in to unmask]
> Subject: Re: lockd for nfs
> 
>>> Has anyone tried to fix the ports that nfs uses for its various daemons?
>
>> # echo "options lockd nlm_udpport=6667 nlm_tcpport=6667" >> 
>> /etc/modprobe.conf
>
> I happened to be looking in to this yesterday.  The only way I can make it 
> work is by putting something in to modprobe.conf (or modprobe.d/something)
>
> It seems that once the kernel module for lockd has loaded, it's too late to 
> change...
>
>   Shane
>
>

-- 
***************************************************************
Eve Kovacs
Argonne National Laboratory,
Room F149, Bldg. 362, HEP
9700 S. Cass Ave.
Argonne, IL 60439 USA
Phone: (630)-252-6208
Fax:   (630)-252-5047
email: [log in to unmask]
***************************************************************

ATOM RSS1 RSS2