/etc/sysconfig/nfs docs?

i don't have an /etc/sysconfig/nfs file on my system. evidently this
is how one tunes the nfs server. have have the nfs-utils rpm.

[root@fs2 init.d]# rpm -q -a | grep nfs
nfs-utils-1.0.6-80.EL4
nfs-utils-lib-1.0.6-8.z1

i can't find anything that directly speaks of what can and can't be
in this file.

thanks.

j.

--
Jay Scott 512-835-3553 gl@arlut.utexas.edu
Head of Sun Support, Sr. Operating Systems Specialist
Applied Research Labs, Computer Science Div. S224
University of Texas at Austin

gl@csdsun1.arlut.utexas.edu (Jay G. Scott) writes:

> i don't have an /etc/sysconfig/nfs file on my system. evidently this
> is how one tunes the nfs server. have have the nfs-utils rpm.
>
> [root@fs2 init.d]# rpm -q -a | grep nfs
> nfs-utils-1.0.6-80.EL4
> nfs-utils-lib-1.0.6-8.z1
>
> i can't find anything that directly speaks of what can and can't be
> in this file.

If your file looks like mine, the file itself documents what can go
into it. It consists of comments and options that are commented out.

You can also see which scripts use all the options by:

# cd /etc/rc.d/init.d
# fgrep -l /etc/sysconfig/nfs *

(You have to be used to reading shell scripts to make the most of this.)

Scott
--
Scott Hemphill hemphill@alumni.caltech.edu
"This isn't flying. This is falling, with style." -- Buzz Lightyear

In article <m3y7d13osq.fsf@jade.local>,
Scott Hemphill <hemphill@alumni.caltech.edu> wrote:
>gl@csdsun1.arlut.utexas.edu (Jay G. Scott) writes:
>
>> i don't have an /etc/sysconfig/nfs file on my system. evidently this
>> is how one tunes the nfs server. have have the nfs-utils rpm.
>>
>> [root@fs2 init.d]# rpm -q -a | grep nfs
>> nfs-utils-1.0.6-80.EL4
>> nfs-utils-lib-1.0.6-8.z1
>>
>> i can't find anything that directly speaks of what can and can't be
>> in this file.
>
>If your file looks like mine, the file itself documents what can go
>into it. It consists of comments and options that are commented out.

i don't have the file. it's not there and zero length, it's flat
not there at all. my attempts to find one online have been less
than comforting. i found something but i'm convinced there's at least
one option not documented in it, and that example was, uh, 3-4 years
old, so i'm not inclined to use it.

thanks for the reply, though. can you tell what rpm is supposed to
be responsible for /etc/sysconfig/nfs? reading between the lines from
the web makes it seem like it should come from nfs-utils, but....

j.

>
>You can also see which scripts use all the options by:
>
># cd /etc/rc.d/init.d
># fgrep -l /etc/sysconfig/nfs *
>
>(You have to be used to reading shell scripts to make the most of this.)
>
>Scott
>--
>Scott Hemphill hemphill@alumni.caltech.edu
>"This isn't flying. This is falling, with style." -- Buzz Lightyear


--
Jay Scott 512-835-3553 gl@arlut.utexas.edu
Head of Sun Support, Sr. Operating Systems Specialist
Applied Research Labs, Computer Science Div. S224
University of Texas at Austin

gl@csdsun1.arlut.utexas.edu (Jay G. Scott) writes:

> In article <m3y7d13osq.fsf@jade.local>,
> Scott Hemphill <hemphill@alumni.caltech.edu> wrote:
> >gl@csdsun1.arlut.utexas.edu (Jay G. Scott) writes:
> >
> >> i don't have an /etc/sysconfig/nfs file on my system. evidently this
> >> is how one tunes the nfs server. have have the nfs-utils rpm.
> >>
> >> [root@fs2 init.d]# rpm -q -a | grep nfs
> >> nfs-utils-1.0.6-80.EL4
> >> nfs-utils-lib-1.0.6-8.z1
> >>
> >> i can't find anything that directly speaks of what can and can't be
> >> in this file.
> >
> >If your file looks like mine, the file itself documents what can go
> >into it. It consists of comments and options that are commented out.
>
> i don't have the file. it's not there and zero length, it's flat
> not there at all. my attempts to find one online have been less
> than comforting. i found something but i'm convinced there's at least
> one option not documented in it, and that example was, uh, 3-4 years
> old, so i'm not inclined to use it.
>
> thanks for the reply, though. can you tell what rpm is supposed to
> be responsible for /etc/sysconfig/nfs? reading between the lines from
> the web makes it seem like it should come from nfs-utils, but....

I'm sorry about not reading your original post carefully enough. The
file is from nfs-utils. Here are the contents of the one from Fedora 8:

==================================snip============ ======================
#
# Define which protocol versions mountd
# will advertise. The values are "no" or "yes"
# with yes being the default
#MOUNTD_NFS_V1="no"
#MOUNTD_NFS_V2="no"
#MOUNTD_NFS_V3="no"
#
#
# Path to remote quota server. See rquotad(8)
#RQUOTAD="/usr/sbin/rpc.rquotad"
# Port rquotad should listen on.
#RQUOTAD_PORT=875
# Optinal options passed to rquotad
#RPCRQUOTADOPTS=""
#
#
# TCP port rpc.lockd should listen on.
#LOCKD_TCPPORT=32803
# UDP port rpc.lockd should listen on.
#LOCKD_UDPPORT=32769
#
#
# Optional arguments passed to rpc.nfsd. See rpc.nfsd(8)
#RPCNFSDARGS
# Number of nfs server processes to be started.
# The default is 8.
#RPCNFSDCOUNT=8
#
#
# Optional arguments passed to rpc.mountd. See rpc.mountd(8)
#RPCMOUNTDOPTS=""
# Port rpc.mountd should listen on.
#MOUNTD_PORT=892
#
#
# Optional arguments passed to rpc.statd. See rpc.statd(8)
#STATDARG=""
# Port rpc.statd should listen on.
#STATD_PORT=662
# Outgoing port statd should used. The default is port
# is random
#STATD_OUTGOING_PORT=2020
# Specify callout program
#STATD_HA_CALLOUT="/usr/local/bin/foo"
#
#
# Optional arguments passed to rpc.idmapd. See rpc.idmapd(8)
#STATDARG=""
# Port rpc.statd should listen on.
#STATD_PORT=662
# Outgoing port statd should used. The default is port
# is random
#STATD_OUTGOING_PORT=2020
# Specify callout program
#STATD_HA_CALLOUT="/usr/local/bin/foo"
#
#
# Optional arguments passed to rpc.idmapd. See rpc.idmapd(8)
#RPCIDMAPDARGS=""
#
# Set to turn on Secure NFS mounts.
#SECURE_NFS="yes"
# Optional arguments passed to rpc.gssd. See rpc.gssd(8)
#RPCGSSDARGS=""
# Optional arguments passed to rpc.svcgssd. See rpc.svcgssd(8)
#RPCSVCGSSDARGS=""
#
==================================snip============ ======================

>
> j.
>
> >
> >You can also see which scripts use all the options by:
> >
> ># cd /etc/rc.d/init.d
> ># fgrep -l /etc/sysconfig/nfs *
> >
> >(You have to be used to reading shell scripts to make the most of this.)

You could examine these scripts to see if they make use of any definitions
not documented above. On my systems, the file is used by

/etc/rc.d/init.d/{nfs,nfslock,rpcgssd,rpcidmapd,rpcsvcgssd}

Scott
--
Scott Hemphill hemphill@alumni.caltech.edu
"This isn't flying. This is falling, with style." -- Buzz Lightyear

[snip]

okay, that file looks just like the one i found on the net.
but it looks incomplete in that there's no way to turn off
nfs version 4. the answer is obvious enough, of course, but
i'm wondering whether that file is out of date in other
respects. anybody know?

in other news -- i'm watching the log files. last night the
server had hiccups every 2 hours. okay, 2 hours + a minute
or two. hiccup == the client would say "not responding still
trying" and then recover in maybe a 45-60 secs, something
like that.

what does THAT mean??? nothing is happening on two hour
intervals that i can think of. it's not a cron job.

j.


--
Jay Scott 512-835-3553 gl@arlut.utexas.edu
Head of Sun Support, Sr. Operating Systems Specialist
Applied Research Labs, Computer Science Div. S224
University of Texas at Austin

Jay G. Scott wrote:
> i don't have an /etc/sysconfig/nfs file on my system. evidently this
> is how one tunes the nfs server. have have the nfs-utils rpm.
>
> [root@fs2 init.d]# rpm -q -a | grep nfs
> nfs-utils-1.0.6-80.EL4
> nfs-utils-lib-1.0.6-8.z1
>
> i can't find anything that directly speaks of what can and can't be
> in this file.

/etc/sysconfig/nfs is used to set environment variables that are used by
/etc/init.d/nfs.

So if you read through /etc/init.d/nfs and find any vars you want to
set, you can put them in /etc/sysconfig/nfs. Mostly they're just
options that are passed to various commands in the script.