On Apr 8, 2008, at 4:48 PM, J. Bruce Fields wrote:
From: Olga Kornievskaia <aglo@xxxxxxxxxxxxxx>
The cl_chatty flag alows us to control whether a given rpc client
leaves
"server X not responding, timed out"
messages in the syslog. Such messages make sense for ordinary nfs
clients (where an unresponsive server means applications on the
mountpoint are probably hanging), but not for the callback client
(which
can fail more commonly, with the only result just of disabling some
optimizations).
Previously cl_chatty was removed, do to lack of users; reinstate
it, and
use it for the nfsd's callback client.
Actually, this might be another candidate for "fail the request
immediately if the transport can't connect."
When exactly do these "server not responding" messages come out?
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
