From: Olaf Kirch <okir@suse.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net, Chuck Lever <chucklever@gmail.com>
Subject: Re: [PATCH 3/4] Add /proc/sys/fs/nfs sysctls to nfsd module
Date: Fri, 4 Aug 2006 19:55:47 +0200 [thread overview]
Message-ID: <20060804175547.GB29852@suse.de> (raw)
In-Reply-To: <1154624881.5774.96.camel@localhost>
> Note, however, that the entire sysctl should be unnecessary. Clients are
> supposed to tell the server how large a reply to return, by means of the
> 'maxcount' argument (see RFC1813). If the clients aren't doing that,
> then they really need to be fixed.
>From a distributor's point of view, waiting for the client vendor to
fix their bugs is often not the best way to go. People buying support
contracts expect a fix, no matter buy whom, they only want it NOW :-)
But I understand if you reject this for upstream.
Olaf
--
Olaf Kirch | --- o --- Nous sommes du soleil we love when we play
okir@suse.de | / | \ sol.dhoop.naytheet.ah kin.ir.samse.qurax
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-08-04 17:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 11:05 [PATCH 3/4] Add /proc/sys/fs/nfs sysctls to nfsd module Olaf Kirch
2006-08-03 16:52 ` Chuck Lever
2006-08-03 17:08 ` Trond Myklebust
2006-08-04 17:55 ` Olaf Kirch [this message]
2006-08-04 8:43 ` Greg Banks
2006-08-04 15:36 ` Trond Myklebust
2006-08-04 17:52 ` Olaf Kirch
2006-08-04 18:23 ` Trond Myklebust
2006-08-04 19:16 ` Peter Staubach
2006-08-04 20:06 ` Olaf Kirch
2006-08-07 4:02 ` Trond Myklebust
2006-08-04 23:36 ` Neil Brown
2006-08-05 13:15 ` Olaf Kirch
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=20060804175547.GB29852@suse.de \
--to=okir@suse.de \
--cc=chucklever@gmail.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.