X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=sgml%2Fadminmanual.sgml;h=0d3d5b21d79095ac093c5ef617fc9acd18017755;hb=05ace8aed12c22b45b8905dacf8de58d79371f5a;hp=9222966b76a6c2e7a168001e9e62b2fc7ef13205;hpb=a52a4d8c59a80d66796429ef2787491581f76326;p=spider.git diff --git a/sgml/adminmanual.sgml b/sgml/adminmanual.sgml index 9222966b..0d3d5b21 100644 --- a/sgml/adminmanual.sgml +++ b/sgml/adminmanual.sgml @@ -7,7 +7,7 @@
+There is now an excellent primer/tutorial on filtering written by Jim
+Samuels, W3BG with an introduction by Dave Hawes N3RD that I strongly
+suggest you read. You can read it here
+
-Below is a complete list of commands available from the cluster prompt.
-Most maintenance tasks are automatic but there are some commands that are useful
-for a sysop. These are listed below in alphabetical order. The number in
-brackets following the command name is the permissions level needed to use
-the command
-
-
-
-
-Create an 'accept this announce' line for a filter.
-
-An accept filter line means that if the announce matches this filter it is
-passed onto the user. See HELP FILTERS for more info. Please read this
-to understand how filters work - it will save a lot of grief later on.
-
-You can use any of the following things in this line:-
-
-
-
-
-This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-
-
-
-
-
-Create an 'accept this routing PC Protocol' line for a filter.
-
-
-An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter
-it is passed thru that interface. See HELP FILTERING for more info. Please read this
-to understand how filters work - it will save a lot of grief later on.
-
-
-You can use any of the following things in this line:-
-
-
-some examples:-
-
-
-You can use the tag 'all' to accept everything eg:
-
-
-
-
-Create an 'accept this spot' line for a filter.
-
-
-An accept filter line means that if the spot matches this filter it is
-passed onto the user. See HELP FILTERS for more info. Please read this
-to understand how filters work - it will save a lot of grief later on.
-
-Please read the following section carefully. Though it looks similar,
-reformatting, corrections, and hopefully clarifications have been added.
-
-You can use any of the following things in this line:-
-
-
-For frequencies, you can use any of the band names defined in
-SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
-thus: hf/ssb. You can also just have a simple range like: 0/30000 -
-this is more efficient than saying simply: freq HF (but don't get
-too hung up about that)
-
-some examples:-
-
-
-
-
-This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-
-
-
-
-
-It is unlikely that you will want to do this, but if you do then you can
-filter on the following fields:-
-
-
-There are no examples because WCY Broadcasts only come from one place and
-you either want them or not (see UNSET/WCY if you don't want them).
-
-This command is really provided for future use.
-
-See HELP FILTER for information.
-
-
-
-
-This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-
-
-
-
-
-It is unlikely that you will want to do this, but if you do then you can
-filter on the following fields:-
-
-
-
-
-This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-
-
-
-
-
-Send an announcement to LOCAL users only, where <text> is the text
-of the announcement you wish to broadcast. If you do not wish to receive
-announces, use the set/noannounce command. Any announces made by
-a sysop will override set/noannounce.
-
-
-
-
-This command will send your announcement across the whole cluster
-network.
-
-
-
-
-
-Send an announcement to Sysops only
-
-
-
-
-Search the help database for <string> (it isn't case sensitive),
-and print the names of all the commands that may be relevant.
-
-
-
-
-This will disconnect you from the cluster
-
-
-
-
-When you send messages the fact that you have forwarded it to another node
-is remembered so that it isn't sent again. When you have a new partner
-node and you add their callsign to your /spider/msg/forward.pl file, all
-outstanding non-private messages will be forwarded to them. This may well
-be ALL the non-private messages. You can prevent this by using these
-commmands:-
-
-
-
-
-A sysop can clear an input or normal output filter for a user or the
-node_default or user_default.
-
-
-
-
-This command allows you to clear (remove) a line in a route filter or to
-remove the whole filter.
-
-see CLEAR/SPOTS for a more detailed explanation.
-
-A sysop can clear an input or normal output filter for a user or the
-node_default or user_default.
-
-
-
-
-This command allows you to clear (remove) a line in a spot filter or to
-remove the whole filter.
-
-If you have a filter:-
-
-
-
-
-A sysop can clear an input or normal output filter for a user or the
-node_default or user_default.
-
-
-
-
-This command allows you to clear (remove) a line in a WCY filter or to
-remove the whole filter.
-
-see CLEAR/SPOTS for a more detailed explanation.
-
-
-
-
-A sysop can clear an input or normal output filter for a user or the
-node_default or user_default.
-
-
-
-
-This command allows you to clear (remove) a line in a WWV filter or to
-remove the whole filter.
-
-see CLEAR/SPOTS for a more detailed explanation.
-
-
-
-
-A sysop can clear an input or normal output filter for a user or the
-node_default or user_default.
-
-
-
-
-Start a connection process that will culminate in a new connection to the
-DX cluster <callsign>. This process creates a new 'client' process which will
-use the script in /spider/connect/<callsign> to effect the 'chat' exchange
-necessary to traverse the network(s) to logon to the cluster <callsign>.
-
-
-
-
-The title says it all really, this command lists all the databases defined
-in the system. It is also aliased to SHOW/COMMAND.
-
-
-
-
-DBCREATE allows you to define a database in the system. It doesn't actually
-create anything, just defines it.
-
-The databases that are created are simple DB_File hash databases, they are
-therefore already 'indexed'.
-
-You can define a local database with the first form of the command eg:
-
- DBCREATE oblast
-
-You can also chain databases with the addition of the 'chain' keyword.
-This will search each database one after the other. A typical example
-is:
-
- DBCREATE sdx_qsl chain sql_ad
-
-No checking is done to see if the any of the chained databases exist, in
-fact it is usually better to do the above statement first then do each of
-the chained databases.
-
-Databases can exist offsite. To define a database that lives on another
-node do:
-
- DBCREATE buckmaster remote gb7dxc
-
-Remote databases cannot be chained; however, the last database in a
-a chain can be a remote database eg:
-
- DBCREATE qsl chain gb7dxc
-
-To see what databases have been defined do:
-
- DBAVAIL (or it will have been aliased to SHOW/COMMAND)
-
-It would be normal for you to add an entry into your local Aliases file
-to allow people to use the 'SHOW/<dbname>' style syntax. So you would
-need to add a line like:-
-
-
-
-
-If you want to import or update data in bulk to a database you can use
-this command. It will either create or update entries into an existing
-database. For example:-
-
- DBIMPORT oblast /tmp/OBLAST.FUL
-
-will import the standard OBLAST database that comes with AK1A into the
-oblast database held locally.
-
-
-
-
-DBREMOVE will completely remove a database entry and also delete any data
-file that is associated with it.
-
-There is no warning, no comeback, no safety net.
-
-For example:
-
- DBREMOVE oblast
-
-will remove the oblast database from the system and it will also remove
-the associated datafile.
-
-I repeat:
-
-There is no warning, no comeback, no safety net.
-
-You have been warned.
-
-
-
-
-This is the generic user interface to the database to the database system.
-It is expected that the sysop will add an entry to the local Aliases file
-so that users can use the more familiar AK1A style of enquiry such as:
-
-
-
-
-Executing this command will only have an effect if you are running the cluster
-in debug mode i.e.
-
-
-
-
-This command will completely remove a one or more users from the database.
-
-There is NO SECOND CHANCE.
-
-It goes without saying that you should use this command CAREFULLY!
-
-
-
-
-This command is provided so that sysops can demonstrate commands to
-other users. It runs a command as though that user had typed it in and
-then sends the output to that user, together with the command that
-caused it.
-
-
-
-
-List the messages in the messages directory.
-
-If there is a 'p' one space after the message number then it is a
-personal message. If there is a '-' between the message number and the
-'p' then this indicates that the message has been read.
-
-You can use shell escape characters such as '*' and '?' in the <call>
-fields.
-
-You can combine some of the various directory commands together eg:-
-
-
-Works just like the user command except that sysops can see ALL messages.
-
-
-
-
-Disconnect any <call> connected locally
-
-
-
-
-This is how you send a DX Spot to other users. You can, in fact, now
-enter the <freq> and the <call> either way round.
-
-
-
-
-Export a message to a file. This command can only be executed on a local
-console with a fully privileged user. The file produced will be in a form
-ready to be imported back into the cluster by placing it in the import
-directory (/spider/msg/import).
-
-This command cannot overwrite an existing file. This is to provide some
-measure of security. Any files written will owned by the same user as the
-main cluster, otherwise you can put the new files anywhere the cluster can
-access. For example:-
-
- EXPORT 2345 /tmp/a
-
-
-
-
-Export the users database to a file in ascii format. If no filename
-is given then it will export the file to /spider/data/user_asc.
-
-If the file already exists it will be renamed to <filename>.o. In fact
-up to 5 generations of the file can be kept each one with an extra 'o' on the
-suffix.
-
-BE WARNED: this will write to any file you have write access to. No check is
-made on the filename (if any) that you specify.
-
-
-
-
-There are a number of things you can filter in the DXSpider system. They
-all use the same general mechanism.
-
-In general terms you can create a 'reject' or an 'accept' filter which
-can have up to 10 lines in it. You do this using, for example:-
-
- accept/spots .....
- reject/spots .....
-
-where ..... are the specific commands for that type of filter. There
-are filters for spots, wwv, announce, wcy and (for sysops)
-connects. See each different accept or reject command reference for
-more details.
-
-There is also a command to clear out one or more lines in a filter and
-one to show you what you have set. They are:-
-
- clear/spots 1
- clear/spots all
-
-and
-
- show/filter
-
-There is clear/xxxx command for each type of filter.
-
-For now we are going to use spots for the examples, but you can apply
-the principles to all types of filter.
-
-There are two main types of filter 'accept' or 'reject'; which you use
-depends entirely on how you look at the world and what is least
-writing to achieve what you want. Each filter has 10 lines (of any
-length) which are tried in order. If a line matches then the action
-you have specified is taken (ie reject means ignore it and accept
-means gimme it).
-
-The important thing to remember is that if you specify a 'reject'
-filter (all the lines in it say 'reject/spots' (for instance) then if
-a spot comes in that doesn't match any of the lines then you will get
-it BUT if you specify an 'accept' filter then any spots that don't
-match are dumped. For example if I have a one line accept filter:-
-
- accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-
-then automatically you will ONLY get VHF spots from or to CQ zones 14
-15 and 16. If you set a reject filter like:
-
- reject/spots on hf/cw
-
-Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
-and will work it even on CW then you could say:-
-
- reject/spots on hf/cw and not info iota
-
-But in that case you might only be interested in iota and say:-
-
- accept/spots not on hf/cw or info iota
-
-which is exactly the same. You should choose one or the other until
-you are confortable with the way it works. Yes, you can mix them
-(actually you can have an accept AND a reject on the same line) but
-don't try this at home until you can analyse the results that you get
-without ringing up the sysop for help.
-
-You can arrange your filter lines into logical units, either for your
-own understanding or simply convenience. I have one set frequently:-
-
- reject/spots 1 on hf/cw
- reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
-
-What this does is to ignore all HF CW spots (being a class B I can't
-read any CW and couldn't possibly be interested in HF :-) and also
-rejects any spots on VHF which don't either originate or spot someone
-in Europe.
-
-This is an exmaple where you would use the line number (1 and 2 in
-this case), if you leave the digit out, the system assumes '1'. Digits
-'0'-'9' are available.
-
-You can leave the word 'and' out if you want, it is implied. You can
-use any number of brackets to make the 'expression' as you want
-it. There are things called precedence rules working here which mean
-that you will NEED brackets in a situation like line 2 because,
-without it, will assume:-
-
- (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
-
-annoying, but that is the way it is. If you use OR - use
-brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
-just 'and by_zone'.
-
-If you want to alter your filter you can just redefine one or more
-lines of it or clear out one line. For example:-
-
- reject/spots 1 on hf/ssb
-
-or
-
- clear/spots 1
-
-To remove the filter in its entirty:-
-
- clear/spots all
-
-There are similar CLEAR commands for the other filters:-
-
- clear/announce
- clear/wcy
- clear/wwv
-
-ADVANCED USERS:-
-
-Once you are happy with the results you get, you may like to experiment.
-
-my example that filters hf/cw spots and accepts vhf/uhf spots from EU
-can be written with a mixed filter, eg:
-
- rej/spot on hf/cw
- acc/spot on 0/30000
- acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
-
-each filter slot actually has a 'reject' slot and an 'accept'
-slot. The reject slot is executed BEFORE the accept slot.
-
-It was mentioned earlier that after a reject test that doesn't match,
-the default for following tests is 'accept', the reverse is true for
-'accept'. In the example what happens is that the reject is executed
-first, any non hf/cw spot is passed to the accept line, which lets
-thru everything else on HF.
-
-The next filter line lets through just VHF/UHF spots from EU.
-
-
-
-
-This command sends all the latitude and longitude information that your
-cluster is holding against callsigns. One advantage of recieving this
-information is that more locator information is held by you. This
-means that more locators are given on the DX line assuming you have
-set/dxgrid enabled. This could be a LOT of information though, so
-it is not recommended on slow links.
-
-
-
-
-This command sends out any information held in the user file which can
-be broadcast in PC41 protocol packets. This information is Name, QTH, Location
-and Homenode. PC41s are only sent for the information that is available.
-
-
-
-
-All commands can be abbreviated, so SHOW/DX can be abbreviated
-to SH/DX, ANNOUNCE can be shortened to AN and so on.
-
-Look at the APROPOS <string> command which will search the help database
-for the <string> you specify and give you a list of likely commands
-to look at with HELP.
-
-
-
-
-This command attempts to re-initialise a link to a (usually) AK1A node
-that has got confused, usually by a protocol loop of some kind. It may
-work - but you usually will be better off simply disconnecting it (or
-better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
-node>).
-
-Best of luck - you will need it.
-
-
-
-
-Delete a message from the local system. You will only be able to
-delete messages that you have originated or been sent (unless you are
-the sysop).
-
-
-
-
-You can get rid of any message to or originating from your callsign using
-this command. You can remove more than one message at a time.
-
-As a sysop you can kill any message on the system.
-
-
-
-
-Delete a message (usually a 'bulletin') from the whole cluster system.
-
-This uses the subject field, so any messages that have exactly the same subject
-will be deleted. Beware!
-
-
-
-
-Deleting a message using the normal KILL commands only marks that message
-for deletion. The actual deletion only happens later (usually two days later).
-
-The KILL EXPUNGE command causes the message to be truly deleted more or less
-immediately.
-
-It otherwise is used in the same way as the KILL command.
-
-
-
-
-
-This is a quick listing that shows which links are connected and
-some information about them. See WHO for a list of all connections.
-
-
-
-
-
-Reload the /spider/cmd/Aliases file after you have editted it. You will need to
-do this if you change this file whilst the cluster is running in order for the
-changes to take effect.
-
-
-
-
-Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
-the cluster is running. This table contains a number of perl regular
-expressions which are searched for in the fields targetted of each message.
-If any of them match then that message is immediately deleted on receipt.
-
-
-
-
-Reload the /spider/data/badwords file if you have changed it manually whilst
-the cluster is running. This file contains a list of words which, if found
-on certain text portions of PC protocol, will cause those protocol frames
-to be rejected. It will all put out a message if any of these words are
-used on the announce, dx and talk commands. The words can be one or
-more on a line, lines starting with '#' are ignored.
-
-
-
-
-Reload the /spider/data/bands.pl file if you have changed it manually whilst
-the cluster is running.
-
-
-
-
-Normally, if you change a command file in the cmd or local_cmd tree it will
-automatially be picked up by the cluster program. Sometimes it can get confused
-if you are doing a lot of moving commands about or delete a command in the
-local_cmd tree and want to use the normal one again. Execute this command to
-reset everything back to the state it was just after a cluster restart.
-
-
-
-
-
-
-If you change the /spider/perl/Messages file (usually whilst fiddling/writing ne
-commands) you can have them take effect during a cluster session by executing this
-command. You need to do this if get something like :-
-
-unknown message 'xxxx' in lang 'en'
-
-
-
-
-Reload the /spider/data/prefix_data.pl file if you have changed it manually
-whilst the cluster is running.
-
-
-
-
-MERGE allows you to bring your spot and wwv database up to date. By default
-it will request the last 10 spots and 5 WWVs from the node you select. The
-node must be connected locally.
-
-You can request any number of spots or wwv and although they will be appended
-to your databases they will not duplicate any that have recently been added
-(the last 2 days for spots and last month for WWV data).
-
-
-
-
-Alter message parameters like To, From, Subject, whether private or bulletin
-or return receipt (RR) is required or whether to keep this message from timing
-out.
-
-
-
-
-Send some arbitrary text to a locally connected callsign. No processing is done on
-the text. This command allows you to send PC Protocol to unstick things if problems
-arise (messages get stuck etc). eg:-
-
- pc gb7djk PC33^GB7TLH^GB7DJK^400^
-
-You can also use in the same way as a talk command to a connected user but
-without any processing, added of "from <blah> to <blah>" or whatever.
-
- pc G1TLH Try doing that properly!!!
-
-
-
-
-his command allows you to send a frame to another cluster node on
-the network and get a return frame. The time it takes to do this
-is a good indication of the quality of the link. The actual time
-it takes is output to the console in seconds.
-Any visible cluster node can be PINGed.
-
-
-
-
-
-This command allows you to send nearly any command to another DX Cluster
-node that is connected to the system.
-
-Whether you get any output is dependant on a) whether the other system knows
-that the node callsign of this cluster is in fact a node b) whether the
-other system is allowing RCMDs from this node and c) whether you have
-permission to send this command at all.
-
-
-
-
-You can read any messages that are sent as 'non-personal' and also any
-message either sent by or sent to your callsign.
-
-
-
-
-
-As a sysop you may read any message on the system
-
-
-
-
-Create an 'reject this announce' line for a filter.
-
-An reject filter line means that if the announce matches this filter it is
-passed onto the user. See HELP FILTERS for more info. Please read this
-to understand how filters work - it will save a lot of grief later on.
-
-You can use any of the following things in this line:-
-
-
-
-
-This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-
-
-
-
-
-Create an 'reject this routing PC Protocol' line for a filter.
-
-
-An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
-it is NOT passed thru that interface. See HELP FILTERING for more info. Please
-read this to understand how filters work - it will save a lot of grief later on.
-You can use any of the following things in this line:-
-
-
-some examples:-
-
-
-You can use the tag 'all' to reject everything eg:
-
-
-
-
-Create a 'reject this spot' line for a filter.
-
-A reject filter line means that if the spot matches this filter it is
-dumped (not passed on). See HELP FILTERS for more info. Please read this
-to understand how filters work - it will save a lot of grief later on.
-
-You can use any of the following things in this line:-
-
-
-
-
-This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-
-
-
-
-
-It is unlikely that you will want to do this, but if you do then you can
-filter on the following fields:-
-
-
-
-
-This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-
-
- reject/wcy gb7djk all
-
-
-
-
-It is unlikely that you will want to do this, but if you do then you can
-filter on the following fields:-
-
-
-
- This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-
-
-
-
-
-You can reply to a message and the subject will automatically have
-"Re:" inserted in front of it, if it isn't already present.
-
-You can also use all the extra qualifiers such as RR, PRIVATE,
-NOPRIVATE, B that you can use with the SEND command (see SEND
-for further details)
-
-
-
-
-All the SEND commands will create a message which will be sent either to
-an individual callsign or to one of the 'bulletin' addresses.
-
-SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
-it will mark the message as personal and send it to the cluster node that
-that callsign is connected to.
-
-You can have more than one callsign in all of the SEND commands.
-
-You can have multiple qualifiers so that you can have for example:-
-
-
-
-
-Literally, record your address details on the cluster.
-
-
-
-
-Allow announce messages to arrive at your terminal.
-
-
-
-
-Set the node_call as an AR-Cluster type node
-
-
-
-
-Setting a word as 'baddx' will prevent spots with that word in the callsign
-field of a DX spot from going any further. They will not be displayed and they
-will not be sent onto other nodes.
-
-The word must be wriiten in full, no wild cards are allowed eg:-
-
-
-
-
-Setting a callsign as a 'badnode' will prevent spots from that node
-going any further. They will not be displayed and they will not be
-sent onto other nodes.
-
-The call can be a full or partial call (or a prefix), eg:-
-
-
-
-
-Setting a callsign as a 'badspotter' will prevent spots from this callsign
-going any further. They will not be displayed and they will not be
-sent onto other nodes.
-
-The call must be written in full, no wild cards are allowed eg:-
-
-
-
-
-Setting a word as a 'badword' will prevent things like spots,
-announces or talks with this word in the the text part from going any
-further. They will not be displayed and they will not be sent onto
-other nodes.
-
-The word must be written in full, no wild cards are allowed eg:-
-
- set/badword annihilate annihilated annihilation
-
-will stop anything with these words in the text.
-
- unset/badword annihilated
-
-will allow text with this word again.
-
-
-
-
-
-Add a beep to DX and other terminal messages.
-
-
-
-
-
-
-Set the node_call as a CLX type node
-
-
-
-
-You can choose to log several different levels. The levels are
-
-chan
-state
-msg
-cron
-connect
-
-You can show what levels you are logging with the show/debug
-command.
-
-You can remove a debug level with unset/debug <name>
-
-
-
-
-You can stop DX messages with the unset/dx command
-
-
-
-
-Some logging programs do not like the additional information at
-the end of a DX spot. If this is the case, use the unset/dxgrid
-command to remove the grid squares.
-
-
-
-
-Set the node_call as a DXNet type node
-
-
-
-
-If you are connected via a telnet session, different implimentations
-of telnet handle echo differently depending on whether you are
-connected via port 23 or some other port. You can use this command
-to change the setting appropriately.
-
-You can remove the echo with the unset/echo command
-
-The setting is stored in your user profile.
-
-YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
-
-
-
-
-If any personal messages come in for your callsign then you can use
-these commands to control whether they are forwarded onto your email
-address. To enable the forwarding do something like:-
-
- SET/EMAIL mike.tubby@somewhere.com
-
-You can have more than one email address (each one separated by a space).
-Emails are forwarded to all the email addresses you specify.
-
-You can disable forwarding by:-
-
- UNSET/EMAIL
-
-
-
-
-Let others on the cluster know you are here by only displaying your
-callsign. If you are away from your terminal you can use the unset/here
-command to let people know you are away. This simply puts brackets
-around your callsign to indicate you are not available.
-
-
-
-
-Tell the cluster system where you normally connect to. Any Messages sent
-to you will normally find their way there should you not be connected.
-eg:-
-
-
-
-
-Set the hop count for a particular type of broadcast for a node.
-
-This command allows you to set up special hop counts for a node
-for currently: announce, spots, wwv and wcy broadcasts.
-
-
-
-
-Connect a node to your system in such a way that you are a full protocol
-member of its network and can see all spots on it, but nothing either leaks
-out from it nor goes back into from the rest of the nodes connected to you.
-
-You can potentially connect several nodes in this way.
-
-You can see which nodes are isolated with the show/isolate (1) command.
-
-You can remove the isolation with the command unset/isolate.
-
-
-
-
-You can select the language that you want the cluster to use. Currently
-the languages available are en (English) and nl (Dutch).
-
-
-
-
-You can set your latitude and longitude manually or alternatively use the
-set/qra command which will do the conversion for you.
-
-
-
-
-In order to get accurate headings and such like you must tell the system
-what your latitude and longitude is. If you have not yet done a SET/QRA
-then this command will set your QRA locator for you. For example:-
-
-
-
-
-Show users and nodes when they log in and out of the local cluster. You
-can stop these messages by using the unset/logininfo command.
-
-
-
-
-
-You can show who is locked out with the show/lockout command.
-To allow the user to connect again, use the unset/lockout command.
-
-
-
-
-Tell the cluster what your name is, eg:-
-
-
-
-
-Tell the system that the call(s) are to be treated as AK1A cluster and
-fed PC Protocol rather normal user commands.
-
-From version 1.41 you can also set the following types of cluster
-
-
-
-
-From version 1.35 onwards neighbouring nodes are pinged at regular intervals (see
-SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
-counter which is decremented on every outgoing ping and then reset to
-the 'obscount' value on every incoming ping. The default value of this
-parameter is 2.
-
-What this means is that a neighbouring node will be pinged twice at
-(default) 300 second intervals and if no reply has been heard just before
-what would be the third attempt, that node is disconnected.
-
-If a ping is heard then the obscount is reset to the full value. Using
-default values, if a node has not responded to a ping within 15 minutes,
-it is disconnected.
-
-
-
-
-Tell the system how many lines you wish on a page when the number of lines
-of output from a command is more than this. The default is 20. Setting it
-explicitly to 0 will disable paging.
-
-
-
-
-This command only works for a 'telnet' user (currently). It will
-only work if you have a password already set. This initial password
-can only be set by the sysop.
-
-When you execute this command it will ask you for your old password,
-then ask you to type in your new password twice (to make sure you
-get it right). You may or may not see the data echoed on the screen
-as you type, depending on the type of telnet client you have.
-
-
-
-
-The password for a user can only be set by a full sysop. The string
-can contain any characters.
-
-The way this field is used depends on context. If it is being used in
-the SYSOP command context then you are offered 5 random numbers and you
-have to supply the corresponding letters. This is now mainly for ax25
-connections.
-
-If it is being used on incoming telnet connections then, if a password
-is set or the:
-
- set/var $main::passwdreq = 1
-
-command is executed in the startup script, then a password prompt is
-given after the normal 'login: ' prompt.
-
-The command "unset/password" is provided to allow a sysop to remove a
-users password completely in case a user forgets or loses their password.
-
-
-
-As from version 1.35 all neighbouring nodes are pinged at regular intervals
-in order to determine the rolling quality of the link and, in future, to
-affect routing decisions. The default interval is 300 secs or 5 minutes.
-
-You can use this command to set a different interval. Please don't.
-
-But if you do the value you enter is treated as minutes up 60 and seconds
-for numbers greater than that.
-
-This is used also to help determine when a link is down at the far end
-(as certain cluster software doesn't always notice), see SET/OBSCOUNT
-for more information.
-
-
-
-
-Set the privilege level on a callsign. The privilege levels that pertain
-to commands are as default:-
-
-
-
-
-Set the node_call as a DXSpider type node
-
-
-
-
-
-
-Tell the system what your QRA (or Maidenhead) locator is. If you have not
-done a SET/LOCATION then your latitude and longitude will be set roughly
-correctly (assuming your locator is correct ;-). For example:-
-
-
-
-
-Tell the system where your are. For example:-
-
-
-
-
-Registration is a concept that you can switch on by executing the
-
- set/var $main::regreq = 1
-
-command (usually in your startup file)
-
-If a user is NOT registered then, firstly, instead of the normal
-motd file (/spider/data/motd) being sent to the user at startup, the
-user is sent the motd_nor file instead. Secondly, the non registered
-user only has READ-ONLY access to the node. The non-registered user
-cannot use DX, ANN etc.
-
-The only exception to this is that a non-registered user can TALK or
-SEND messages to the sysop.
-
-To unset a user use the 'unset/register' command
-
-
-
-
-Allow talk messages to arrive at your console. You can switch off
-talks with the unset/talk command.
-
-
-
-
-Allow WCY information to be seen at your console. You can switch off
-WCY messages with the unset/wcy command.
-
-
-
-
-Allow WWV information to be seen at your console. You can switch off
-WWV messages with the unset/wwv command.
-
-
-
-
-Allow WX information to be seen at your console. You can switch off
-WX messages with the unset/wx command.
-
-
-
-
-Display all the bad dx callsigns in the system, see SET/BADDX
-for more information.
-
-
-
-
-Display all the bad node callsigns in the system, see SET/BADNODE
-for more information.
-
-
-
-
-Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
-for more information.
-
-
-
-
-Display all the bad words in the system, see SET/BADWORD
-for more information.
-
-
-
-
-This command allows you to see all the users that can be seen
-and the nodes to which they are connected. With the optional node,
-you can specify a particular node to look at.
-
-This command is normally abbreviated to: sh/c
-
-BE WARNED: the list that is returned can be VERY long
-
-
-
-
-Show all the nodes connected locally and the nodes they have connected.
-
-
-
-