--- loncom/Attic/lonManage 2003/09/08 09:45:20 1.14 +++ loncom/Attic/lonManage 2003/09/16 09:49:54 1.15 @@ -3,9 +3,9 @@ # # lonManage supports remote management of nodes in a LonCAPA cluster. # -# $Id: lonManage,v 1.14 2003/09/08 09:45:20 foxr Exp $ +# $Id: lonManage,v 1.15 2003/09/16 09:49:54 foxr Exp $ # -# $Id: lonManage,v 1.14 2003/09/08 09:45:20 foxr Exp $ +# $Id: lonManage,v 1.15 2003/09/16 09:49:54 foxr Exp $ # # Copyright Michigan State University Board of Trustees # @@ -36,7 +36,7 @@ # lonManage -push newfile host # Push to the lonTabs directory. Note that # must be one of: -# hosts (hosts.tab) +# host (hosts.tab) # domain (domain.tab) # # lonManage -reinit lonc host @@ -50,6 +50,10 @@ # not the IP address of the host. # # $Log: lonManage,v $ +# Revision 1.15 2003/09/16 09:49:54 foxr +# Adjust the usage message to reflect what actually will happen on +# --reinit={lond|lonc} +# # Revision 1.14 2003/09/08 09:45:20 foxr # Remove BUGBUG about comment about authentication as we'll be doing # host based authentication initially (no need for lonManage to do anything), @@ -126,15 +130,18 @@ sub Usage { lonManage --push= newfile host Push to the lonTabs directory. Note that must be one of: - hosts (hosts.tab) + host (hosts.tab) domain (domain.tab) lonManage --reinit=lonc host - Sends a HUP signal to the remote systems's lond. + Causes lonc in the remote system to reread hosts.tab and + adjust the set of clients that are being maintained to match + the new file. + lonManage --reinit=lond host - Requests the remote system's lond perform the same action as if - it had received a HUP signal. + Causes lond in the remote system to reread the hosts.tab file + and adjust the set of servers to match changes in that file. In the above syntax, the host above is the hosts.tab name of a host, not the IP address of the host.