+ 9\b9.\b.8\b8.\b. B\bBB\bBS\bS i\bin\bnt\bte\ber\brf\bfa\bac\bce\be
+
+ Spider provides a simple BBS interface. No input is required from the
+ sysop of the cluster at all. The BBS simply sets the cluster as a BBS
+ and pushes any required mail to the cluster. No mail can flow from
+ Spider to the BBS, the interface is one-way.
+
+
+ Please be careful not to flood the cluster network with unnecessary
+ mail. Make sure you only send mail to the clusters that want it by
+ using the Forward.pl file very carefully.
+
+
+ 9\b9.\b.9\b9.\b. U\bUp\bpd\bda\bat\bti\bin\bng\bg k\bke\bep\bpl\ble\ber\br d\bda\bat\bta\ba
+
+ 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 _\be_\bx_\bp_\bo_\br_\bt 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 _\bc_\bo_\bn_\bv_\bk_\be_\bp_\bs_\b._\bp_\bl. 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.
+
+
+