Linux NFS development
 help / color / mirror / Atom feed
From: Matt Schillinger <mschilli@vss.fsi.com>
To: nfs@lists.sourceforge.net
Subject: Typo in Redhat 8/9 nfs start/stop script
Date: 19 Jun 2003 14:27:44 -0500	[thread overview]
Message-ID: <1056050865.15737.282.camel@mosix> (raw)

Note for any Redhat users that need higher than default input queues for
NFS.


# Get the initial values for the input sock queues
# at the time of running the script.
if [ "$TUNE_QUEUE" = "yes" ]; then
    RMEM_DEFAULT=`/sbin/sysctl -n net.core.rmem_default`
    RMEM_MAX=`/sbin/sysctl -n net.core.rmem_max`
    # 256kb recommended minimum size based on SPECsfs NFS benchmarks
    [ -z "$NFS_QS" ] && NFS_QS=262144
fi

# See how we were called.
case "$1" in
  start)
        # Start daemons.
        # Apply input queue increase for nfs server
        if [ "$TUNE_QUEUE" = "yes" ]; then
            /sbin/sysctl -w net.core.rmem_default=$NFSD_QS >/dev/null
2>&1
            /sbin/sysctl -w net.core.rmem_max=$NFSD_QS >/dev/null 2>&1
        fi



NOTE THAT when checking that the variable has a value and setting the
variable, NFS_QS is used. But when setting the input queues, $NFSD_QS is
used.


-- 
Matt Schillinger

mschilli@vss.fsi.com





-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2003-06-19 19:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-19 19:27 Matt Schillinger [this message]
2003-06-21 12:51 ` Typo in Redhat 8/9 nfs start/stop script Steve Dickson
  -- strict thread matches above, loose matches on Subject: below --
2003-06-19 20:50 pwitting
2003-06-20 13:37 ` Matt Schillinger
2003-06-20 14:30   ` James Pearson
2003-06-20 14:39 pwitting
2003-06-23 17:55 pwitting
2003-06-24 12:19 ` Steve Dickson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1056050865.15737.282.camel@mosix \
    --to=mschilli@vss.fsi.com \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox