X-Git-Url: http://dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fadminmanual-9.html;h=a002c013bd9eabc23f1db3c84332eb207b459864;hb=db143ea6ee006dd7ffc360fcf022459d68412976;hp=6f0d0ef62a7d73b7c4b96f309357d67a47f9618a;hpb=59e40dfc42f6e9046859fa66ff6465417e4f1750;p=spider.git diff --git a/html/adminmanual-9.html b/html/adminmanual-9.html index 6f0d0ef6..a002c013 100644 --- a/html/adminmanual-9.html +++ b/html/adminmanual-9.html @@ -394,6 +394,42 @@ the interface is one-way. Make sure you only send mail to the clusters that want it by using the Forward.pl file very carefully.

+

9.9 Updating kepler data +

+ +

Spider has a powerful and flexible show/satellite command. In order for +this to be accurate, the kepler data has to be updated regularly. In +general, this data is available as an email or via cluster mail. +Updating it is simple. First you need to export the mail message as a +file. You do this with the export command from the cluster prompt +as the sysop. For example ... +

+

+
+export 5467 /spider/perl/keps.in
+
+
+

would export message number 5467 as a file called keps.in in the +/spider/perl directory. +

Now login to a VT as sysop and cd /spider/perl. There is a command in +the perl directory called convkeps.pl. All we need to do now is +convert the file like so ... +

+

+
+./convkeps.pl keps.in
+
+
+

Now go back to the cluster and issue the command ... +

+

+
+load/keps
+
+
+

That is it! the kepler data has been updated. +

+

Next Previous