* tramp.texi (Connection caching): Tramp flushes connection

properties when remote operating system has been changed.

2 files changed, 22 insertions, 3 deletions

diff --git a/doc/misc/ChangeLog b/doc/misc/ChangeLog
index 63f9a6e596f..40e824cfba6 100644
--- a/doc/misc/ChangeLog
+++ b/doc/misc/ChangeLog
@@ -1,3 +1,8 @@
+2007-11-12  Michael Albinus  <michael.albinus@gmx.de>
+
+        * tramp.texi (Connection caching): Tramp flushes connection
+        properties when remote operating system has been changed.
+
 2007-11-09  Reiner Steib  <Reiner.Steib@gmx.de>
 
         * gnus-news.texi: Fix spelling.
diff --git a/doc/misc/tramp.texi b/doc/misc/tramp.texi
index 591122640fe..127ccd11024 100644
--- a/doc/misc/tramp.texi
+++ b/doc/misc/tramp.texi
@@ -327,9 +327,10 @@ host, followed by a newline.
 @value{tramp} now waits for the shell prompt or for a message that the login
 failed.
 
-If @value{tramp} sees neither of them after a certain period of time (a minute,
-say), then it issues an error message saying that it couldn't find the
-remote shell prompt and shows you what the remote host has sent.
+If @value{tramp} sees neither of them after a certain period of time
+(a minute, say), then it issues an error message saying that it
+couldn't find the remote shell prompt and shows you what the remote
+host has sent.
 
 If @value{tramp} sees a @samp{login failed} message, it tells you so,
 aborts the login attempt and allows you to try again.
@@ -1602,6 +1603,19 @@ the connections, like introducing a @option{Host} section in
 @file{~/.ssh/config} (@pxref{Frequently Asked Questions}) or applying
 multiple hops (@pxref{Multi-hops}).
 
+When @value{tramp} detects a changed operating system version on a
+remote host (via the command @command{uname -sr}), it flushes all
+connection related information for this host, quits the execution, and
+displays a message like this:
+
+@example
+Quit: "Connection reset, because remote host changed from `Linux
+2.6.22-13-generic' to `Linux 2.6.22-14-generic'"
+@end example
+
+@noindent
+You can simply open the remote file again in such a case.
+
 
 @node Remote Programs
 @section How @value{tramp} finds and uses programs on the remote machine.