X-Git-Url: http://dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;ds=sidebyside;f=html%2Fclient.html;h=e62e22a4843516bd7fca98ba091171209c4a2685;hb=24e7cdb8b2479635fc99952e007bfc6c4c7f6a9a;hp=b63ec801eef7c80768e2c44767300fbddcbd94f9;hpb=c4284750b659c9f1ce58119a13daf4c52e3c1e38;p=spider.git diff --git a/html/client.html b/html/client.html index b63ec801..e62e22a4 100644 --- a/html/client.html +++ b/html/client.html @@ -2,10 +2,10 @@
-Last modified: Mon Dec 21 12:26:18 GMT 1998 +Last modified: Sun Apr 1 18:18:19 BST 2001
There is a related program called /spider/perl/console.pl which, + as of version 1.30, is the standard sysop or full duplex telnet user + connected interface program. This is a simple screen oriented program + that has a bash or shell like command history editing facility as well + as a scrolling cluster window with colouration of particular lines of + interest (such as DX spots, Announces etc). + -
The client can take up two arguments: a "callsign" and a connection type. @@ -44,25 +51,16 @@ Last modified: Mon Dec 21 12:26:18 GMT 1998
For incoming connections it is important to make sure that +
For normal incoming ax25 connections it is important to make sure that the callsign passed DOES NOT have an SSID (use the %u or %U in ax25d.conf). The DXSpider system largely ignores what it regards as 'duplicate' callsigns (and that includes those with SSIDs) except in certain special cases. -
Also in 1.13 only existing users can enter via this means. This will probably - change, but please discuss this in the support - mailing list. -
The connection type can be:- @@ -70,9 +68,6 @@ Last modified: Mon Dec 21 12:26:18 GMT 1998
The connection type can be missing in which case the default is unix line conventions. @@ -103,9 +98,19 @@ Last modified: Mon Dec 21 12:26:18 GMT 1998 The client only uses files when in the login phase. It prints the /spider/data/issue file, if it is present, to the user before issuing the login: prompt. After a callsign - and password is entered it uses - the standard cluster user file to check them. - + is entered it uses + the standard cluster user file to check it. + +
Having said all of that the client appears to use the following files and + sends them to the user if they are present:- +