Increase the default timeout for PingIntervalSeconds from 15 to 60 and update

docs to highlight how this feature works, since the previous docs were
misleading.  Fixes bug #606861.

1 files changed, 7 insertions, 6 deletions

diff --git a/docs/C/gdm.xml b/docs/C/gdm.xml
index 87941e0e..8ad3046d 100644
--- a/docs/C/gdm.xml
+++ b/docs/C/gdm.xml
@@ -1528,13 +1528,14 @@ gdm:.my.domain
           <varlistentry>
             <term>PingIntervalSeconds</term>
             <listitem>
-              <synopsis>PingIntervalSeconds=15</synopsis>
+              <synopsis>PingIntervalSeconds=60</synopsis>
               <para>
-                Interval in which to ping the Xserver in seconds.  If the
-                Xserver does not respond before the next time we ping it, the
-                connection is stopped and the session ended.  This is a
-                combination of the XDM PingInterval and PingTimeout, but in
-                seconds.
+                If the Xserver does not respond in the specified number of
+                seconds, then the connection is stopped and the session ended.
+                When this happens the slave daemon dies with an ALARM signal.
+                Note that GDM 2.20 and earlier multiplied this setting by 2,
+                so it may be necessary to increase the timeout if upgrading
+                from GDM 2.20 and earlier to a newer version.
               </para>
 
               <para>