All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Dsouza <kdsouza-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: manpage: update mount.cifs manpage with info about echo_interval option.
Date: Tue, 23 Jan 2018 23:07:16 +0530	[thread overview]
Message-ID: <CAA_-hQJ=DsbeVWU7mr-W0sTRiPXnCC3vznmznQwBedQLtE0s_g@mail.gmail.com> (raw)

Signed-off-by:  Kenneth D'souza <kdsouza-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

diff --git a/mount.cifs.rst b/mount.cifs.rst
index 023ff34..efd7055 100644
--- a/mount.cifs.rst
+++ b/mount.cifs.rst
@@ -385,6 +385,14 @@ mfsymlinks
   option. Minshall+French symlinks are used even if the server supports
   the CIFS Unix Extensions.

+echo_interval=n
+  sets the interval at which echo requests are sent to the server on an
+  idling connection. This setting also affects the time required
+  for a connection to an unresponsive server to timeout.
+  Here n is the echo interval in seconds. If this option is not given then
+  the default value of 60 seconds is used.
+  The minimum tunable value is 1 second and maximum can go up to 600 seconds.
+
 serverino
   Use inode numbers (unique persistent file identifiers) returned by the
   server instead of automatically generating temporary inode numbers on




Kind Regards,
Kenneth D'souza

             reply	other threads:[~2018-01-23 17:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23 17:37 Kenneth Dsouza [this message]
     [not found] ` <CAA_-hQJ=DsbeVWU7mr-W0sTRiPXnCC3vznmznQwBedQLtE0s_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-23 23:05   ` manpage: update mount.cifs manpage with info about echo_interval option Steve French
2018-01-24 10:40   ` Aurélien Aptel
     [not found]     ` <87y3knsfpa.fsf-IBi9RG/b67k@public.gmane.org>
2018-01-24 10:53       ` Sachin Prabhu
     [not found]         ` <1516791183.20341.2.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-01-24 11:14           ` Aurélien Aptel
     [not found]             ` <87shavse4a.fsf-IBi9RG/b67k@public.gmane.org>
2018-01-24 12:35               ` Sachin Prabhu

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='CAA_-hQJ=DsbeVWU7mr-W0sTRiPXnCC3vznmznQwBedQLtE0s_g@mail.gmail.com' \
    --to=kdsouza-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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.