[LON-CAPA-cvs] cvs: loncom /lonnet/perl lonnet.pm

[www]

www		Fri Dec  6 07:55:44 2002 EDT

  Modified files:              
    /loncom/lonnet/perl	lonnet.pm 
  Log:
  Guy is correct, the sleep in critical does not make sense. Yet, &reply does
  have to be given two tries, since only when trying the first one might lonc
  detect that the connection is down. lonc then needs to be given time to try
  and re-establish the connection.
  
  
Index: loncom/lonnet/perl/lonnet.pm
diff -u loncom/lonnet/perl/lonnet.pm:1.309 loncom/lonnet/perl/lonnet.pm:1.310
--- loncom/lonnet/perl/lonnet.pm:1.309	Thu Dec  5 18:51:05 2002
+++ loncom/lonnet/perl/lonnet.pm	Fri Dec  6 07:55:44 2002
@@ -1,7 +1,7 @@
 # The LearningOnline Network
 # TCP networking package
 #
-# $Id: lonnet.pm,v 1.309 2002/12/05 23:51:05 albertel Exp $
+# $Id: lonnet.pm,v 1.310 2002/12/06 12:55:44 www Exp $
 #
 # Copyright Michigan State University Board of Trustees
 #
@@ -143,8 +143,8 @@
     unless (defined($hostname{$server})) { return 'no_such_host'; }
     my $answer=subreply($cmd,$server);
     if ($answer eq 'con_lost') {
-       #sleep 5; 
-       #$answer=subreply($cmd,$server);
+       sleep 5; 
+       $answer=subreply($cmd,$server);
        #if ($answer eq 'con_lost') {
 	#   &logthis("Second attempt con_lost on $server");
         #   my $peerfile="$perlvar{'lonSockDir'}/$server";
@@ -203,7 +203,6 @@
                " Critical message to unknown server ($server)</font>");
         return 'no_such_host';
     }
-    sleep 2;
     my $answer=reply($cmd,$server);
     if ($answer eq 'con_lost') {
         my $pingreply=reply('ping',$server);