[BACK]Return to lonManage CVS log [TXT] [DIR] Up to [LON-CAPA] / loncom

Diff for /loncom/Attic/lonManage between versions 1.1 and 1.6

version 1.1, 2003/08/12 09:46:27 version 1.6, 2003/08/12 11:02:59
Line 49 Line 49
 #    In the above syntax, the host above is the hosts.tab name of a host,  #    In the above syntax, the host above is the hosts.tab name of a host,
 #    not the IP address of the host.  #    not the IP address of the host.
 #  #
   #  $Log$
   #  Revision 1.6  2003/08/12 11:02:59  foxr
   #  Implement command switch dispatching.
   #
   #  Revision 1.5  2003/08/12 10:55:42  foxr
   #  Complete command line parsing (tested)
   #
   #  Revision 1.4  2003/08/12 10:40:44  foxr
   #  Get switch parsing right.
   #
   #  Revision 1.3  2003/08/12 10:22:35  foxr
   #  Put in parameter parsing infrastructure
   #
   #  Revision 1.2  2003/08/12 09:58:49  foxr
   #  Add usage and skeleton documentation.
   #
   #
   use Getopt::Long;
   
   sub Usage  {
       print "Usage:";
       print <<USAGE;
       lonManage  --push=<tablename>  newfile  host
           Push <tablename> to the lonTabs directory.  Note that
           <tablename> must be one of:
              hosts  (hosts.tab)
              domain (domain.tab)
   
       lonManage  --reinit=lonc host
              Sends a HUP signal to the remote systems's lond.
   
       lonmanage  --reinit=lond host
             Requests the remote system's lond perform the same action as if
             it had received a HUP signal.
   
       In the above syntax, the host above is the hosts.tab name of a host,
       not the IP address of the host.
   USAGE
   
   
   }
   
   #
   #  Use Getopt::Long to parse the parameters of the program.
   #
   #  Return value is a list consisting of:
   #    A 'command' which is one of:
   #       push   - table push requested.
   #       reinit - reinit requested.
   #   Additional parameters as follows:
   #       for push: Tablename, hostname
   #       for reinit: Appname  hostname
   #
   #   This function does not validation of the parameters of push and
   #   reinit.
   #
   #   returns a list.  The first element of the list is the operation name
   #   (e.g. reinit or push).  The second element is the switch parameter.
   #   for push, this is the table name, for reinit, this is the process name.
   #   Additional elements of the list are the command argument.  The count of
   #   command arguments is validated, but not their semantics.
   #
   #   returns an empty list if the parse fails.
   #
   
   sub ParseArgs {
       my $pushing   = '';
       my $reiniting = '';
   
       if(!GetOptions('push=s'    => \$pushing,
              'reinit=s'  => \$reinitting)) {
    return ();
       }
   
       #  Require exactly   one of --push and --reinit
   
       my $command    = '';
       my $commandarg = '';
       my $paramcount = @ARGV; # Number of additional arguments.
       
   
       if($pushing ne '') {
   
           # --push takes in addition a table, and a host:
           #
    if($paramcount != 2) {
       return (); # Invalid parameter count.
    }
    if($command ne '') {
       return ();
    } else {
       
       $command    = 'push';
       $commandarg = $pushing;
    }
       }
   
       if ($reinitting ne '') {
   
    # --reinit takes in addition just a host name
   
    if($paramcount != 1) {
       return ();
    }
    if($command ne '') {
       return ();
    } else {
       $command    = 'reinit';
       $commandarg = $reinitting; 
    }
       }
   
       #  Build the result list:
   
       my @result = ($command, $commandarg);
       my $i;
       for($i = 0; $i < $paramcount; $i++) {
    push(@result, $ARGV[$i]);
       }
       
       return @result;
   }
   
   #--------------------------- Entry point: --------------------------
   
   #  Parse the parameters
   #  If command parsing failed, then print usage:
   
   @params = ParseArgs;
   $nparam   = @params;
   
   if($nparam == 0) {
       Usage;
       exit -1;
   }
   
   
   sub PushFile {
       print "Pushing a file\n";
   }
   
   sub ReinitProcess {
       print "Reinitializing a process\n";
   }
   
   #   Based on the operation requested invoke the appropriate function:
   
   $operation = shift @params;
   
   if($operation eq "push") {  # push tablename filename host
       $tablename = shift @params;
       $tablefile = shift @params;
       $host      = shift @params;
       PushFile($tablename, $tablefile, $host);
   
   }
   if($operation eq "reinit") { # reinit processname host.
       $process   = shift @params;
       $host      = shift @params;
       ReinitProcess($process, $host);
   }
   exit 0;
   
   =head1 NAME
       lonManage - Command line utility for remote management of lonCAPA
       cluster nodes.
   
   =head1 SYNOPSIS
   
   Usage:
       B<lonManage  --push=<tablename>  newfile  host>
           Push <tablename> to the lonTabs directory.  Note that
           <tablename> must be one of:
              hosts  (hosts.tab)
              domain (domain.tab)
   
       B<lonManage  --reinit=lonc host>
              Sends a HUP signal to the remote systems's lond.
   
       B<lonmanage  --reinit=lond host>
             Requests the remote system's lond perform the same action as if
             it had received a HUP signal.
   
       In the above syntax, the host above is the hosts.tab name of a host,
       not the IP address of the host.
   
   
   =head1 DESCRIPTION
   
   =head1 PREREQUISITES
   
   =item Getopt::Long
   
   =head1  CATEGORIES
       Command line utility
   
   =cut
Removed from v.1.1  
changed lines
  Added in v.1.6

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>