[LON-CAPA-cvs] cvs: loncom / clusteradmin

raeburn raeburn@source.lon-capa.org
Thu, 12 May 2011 14:08:55 -0000

raeburn		Thu May 12 14:08:55 2011 EDT

  Modified files:              
    /loncom	clusteradmin 
  - Fix typos in documentation.
  - Skip update of dns_*.tab files on server where clusteradmin is being run.
Index: loncom/clusteradmin
diff -u loncom/clusteradmin:1.3 loncom/clusteradmin:1.4
--- loncom/clusteradmin:1.3	Wed May 13 19:58:32 2009
+++ loncom/clusteradmin	Thu May 12 14:08:54 2011
@@ -8,7 +8,7 @@
-Performs an adiminstrative action on all hosts in the current dns_hosts.tab
+Performs an adminstrative action on DNS hosts in the current hosts.tab
 file.  For this to work, the current host must be the cluster administrator
 on the target systems.  That is this must be a host in managers.tab
 Furthermore, lonc must be running on this system.
@@ -16,7 +16,7 @@
 The action is specified by the 'command' parameter which may have additional arguments.
 All communications with remote clients are made critical so that
-they will eventually happen even if the147 host we want to talk with
+they will eventually happen even if the host we want to talk with
 is dead.
@@ -219,6 +219,7 @@
     foreach my $host (@$hosts) {
 	my $loncapa_name = &Apache::lonnet::host_from_dns($host);
+        next if ($loncapa_name eq $config{'lonHostID'});
 	my $reply  = &Apache::lonnet::critical($cmd, $loncapa_name);
 	if ($reply ne 'ok') {
 	    print STDERR "Reply from $host ($loncapa_name)  not 'ok' was: $reply\n";