From: g0vgs Date: Tue, 18 Mar 2003 18:23:26 +0000 (+0000) Subject: minor corrections to manuals X-Git-Tag: PRE-1-52~9 X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=commitdiff_plain;h=90a05bee744c82d66ffdd0a0548b2ae97d7dfb56;p=spider.git minor corrections to manuals --- diff --git a/Changes b/Changes index 3124f8fc..f2de3ed0 100644 --- a/Changes +++ b/Changes @@ -1,3 +1,5 @@ +18Mar03======================================================================= +1. minor corrections to manuals (g0vgs) 12Mar03======================================================================= 1. added HC and QRZ.com to possible QSL locations, if you want to pick up historical info (ie start again), run create_qsl.pl after update and restart diff --git a/html/adminmanual_en-11.html b/html/adminmanual_en-11.html index 3caad921..e9fc6871 100644 --- a/html/adminmanual_en-11.html +++ b/html/adminmanual_en-11.html @@ -331,7 +331,97 @@ the filter will be completely removed.

dbavail Show a list of all the Databases in the system

Title says it all really, this command lists all the databases definedin the system. It is also aliased to SHOW/COMMAND.

-

11.30 dbshow <dbname> <key> (0) +

11.30 dbcreate <name> (9) +

+ +

dbcreate <name> Create a database entry

+ +

11.31 dbcreate <name> chain <name> [<name>..] (9) +

+ +

dbcreate <name> chain <name> [<name>..] Create a chained database entry

+ +

11.32 dbcreate <name> cmd <dxspider command> (9) +

+ +

dbcreate <name> cmd <dxspider command> make a local command available as a DB

+

DBCREATE allows you to define a database in the system. It doesn't actuallycreate 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, infact it is usually better to do the above staement first then do each ofthe 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 fileto allow people to use the 'SHOW/<dbname>' style syntax. So you wouldneed to add a line like:- +
+
+  's' => [    ..    ..    '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',    ..    ..   ],
+
+
+to allow +
+
+  SH/BUCK g1tlh
+
+
+to work as they may be used to.You can also make local commands available as 'pseudo' databases. Youcan therefore make spider special commands available as a database. Iimagine that this will be primarily useful for remote access from legacy nodes. For example:- +
+
+  DBCREATE dxqsl cmd show/dxqsl
+
+
+You also use one of these databases in a chain. This may be useful locally. See DBIMPORT for the importing of existing AK1A format data to databases.See DBSHOW for generic database enquiry

+

11.33 dbcreate <name> remote <node> (9) +

+ +

dbcreate <name> remote <node> Create a remote database entry

+ +

11.34 dbimport <dbname> <filename> (9) +

+ +

dbimport <dbname> <filename> Import AK1A data into a database

+

If you want to import or update data in bulk to a database you can usethis command. It will either create or update entries into an existingdatabase. For example:- +

+
+  DBIMPORT oblast /tmp/OBLAST.FUL
+
+
+will import the standard OBLAST database that comes with AK1A into theoblast database held locally.

+

11.35 dbremove <dbname> (9) +

+ +

dbremove <dbname> Delete a database

+

DBREMOVE will completely remove a database entry and also delete any datafile 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 removethe associated datafile.I repeat:There is no warning, no comeback, no safety net.You have been warned.

+

11.36 dbshow <dbname> <key> (0)

dbshow <dbname> <key> Display an entry, if it exists, in a database

@@ -348,12 +438,44 @@ but if he hasn't and the database really does exist (use DBAVAIL orSHOW/COMMAND

-

11.31 directory (0) +

11.37 debug (9) +

+ +

debug Set the cluster program into debug mode

+

Executing this command will only have an effect if you are running the clusterin debug mode i.e. +

+
+        perl -d cluster.pl
+
+
+It will interrupt the cluster just after the debug command has finished.

+

11.38 delete/usdb <callsign> ... (9) +

+ +

delete/usdb <callsign> ... Delete this user from the US State Database

+

This command will completely remove a one or more callsignsfrom the US States database.There is NO SECOND CHANCE.It goes without saying that you should use this command CAREFULLY!Note that these callsign may be re-instated by any weekly updates from the FCC.

+

11.39 delete/user <callsign> ... (9) +

+ +

delete/user <callsign> ... Delete this user from the User Database

+

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!

+

11.40 demonstrate <call> <command> (9) +

+ +

demonstrate <call> <command> Demonstrate a command to another user

+

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 andthen sends the output to that user, together with the command that caused it. +

+
+  DEMO g7brn sh/dx iota oc209  DEMO g1tlh set/here
+
+
+Note that this command is similar to SPOOF and will have the same sideeffects. Commands are run at the privilege of the user which is beingdemonstrated to.

+

11.41 directory (0)

directory List messages

-

11.32 directory <from>-<to> (0) +

11.42 directory <from>-<to> (0)

directory <from>-<to> List messages <from> message <to> message

@@ -376,52 +498,52 @@ You can abbreviate all the commands to one letter and use ak1a syntax:-

-

11.33 directory <nn> (0) +

11.43 directory <nn> (0)

directory <nn> List last <nn> messages

-

11.34 directory all (0) +

11.44 directory all (0)

directory all List all messages

-

11.35 directory from <call> (0) +

11.45 directory from <call> (0)

directory from <call> List all messages from <call>

-

11.36 directory new (0) +

11.46 directory new (0)

directory new List all new messages

-

11.37 directory own (0) +

11.47 directory own (0)

directory own List your own messages

-

11.38 directory subject <string> (0) +

11.48 directory subject <string> (0)

directory subject <string> List all messages with <string> in subject

-

11.39 directory to <call> (0) +

11.49 directory to <call> (0)

directory to <call> List all messages to <call>

-

11.40 directory- (5) +

11.50 directory- (5)

directory-

Sysops can see all users' messages.

-

11.41 disconnect <call> [<call> ...] (8) +

11.51 disconnect <call> [<call> ...] (8)

disconnect <call> [<call> ...] Disconnect a user or cluster

Disconnect any <call> connected locally

-

11.42 dx [by <call>] <freq> <call> <remarks> (0) +

11.52 dx [by <call>] <freq> <call> <remarks> (0)

dx [by <call>] <freq> <call> <remarks> Send a DX spot

@@ -444,7 +566,7 @@ You can credit someone else by saying:- The <freq> is compared against the available bands set up in the cluster. See SHOW/BANDS for more information.

-

11.43 echo <line> (0) +

11.53 echo <line> (0)

echo <line> Echo the line to the output

@@ -479,7 +601,23 @@ produces:- on the output.

-

11.44 filtering... (0) +

11.54 export <msgno> <filename> (9) +

+ +

export <msgno> <filename> Export a message to a file

+

Export a message to a file. This command can only be executed on a localconsole with a fully privileged user. The file produced will be in a formready 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 canaccess. For example:- +

+
+  EXPORT 2345 /tmp/a
+
+
+

+

11.55 export_users [<filename>] (9) +

+ +

export_users [<filename>] Export the users database to ascii

+

Export the users database to a file in ascii format. If no filenameis 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 factup to 5 generations of the file can be kept each one with an extra 'o' on thesuffix. BE WARNED: this will write to any file you have write access to. No check ismade on the filename (if any) that you specify.

+

11.56 filtering... (0)

filtering... Filtering things in DXSpider

@@ -574,17 +712,17 @@ ADVANCED USERS:-Once you are happy with the results you get, you may like to exp 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 executedfirst, any non hf/cw spot is passed to the accept line, which letsthru everything else on HF.The next filter line lets through just VHF/UHF spots from EU.

-

11.45 forward/latlong <node_call> (8) +

11.57 forward/latlong <node_call> (8)

forward/latlong <node_call> Send latitude and longitude information to another cluster

This command sends all the latitude and longitude information that yourcluster is holding against callsigns. One advantage of recieving thisinformation is that more locator information is held by you. Thismeans that more locators are given on the DX line assuming you haveSET/DXGRID enabled. This could be a LOT of information though, soit is not recommended on slow links.

-

11.46 forward/opernam <call> (1) +

11.58 forward/opernam <call> (1)

forward/opernam <call> Send out information on this <call> to all clusters

This command sends out any information held in the user file which can be broadcast in PC41 protocol packets. This information is Name, QTH, Locationand Homenode. PC41s are only sent for the information that is available.

-

11.47 help (0) +

11.59 help (0)

help The HELP Command

@@ -595,47 +733,47 @@ each filter slot actually has a 'reject' slot and an 'accept'slot. The reject sl Where <cmd> is the name of the command you want help on.All commands can be abbreviated, so SHOW/DX can be abbreviatedto SH/DX, ANNOUNCE can be shortened to AN and so on.Look at the APROPOS <string> command which will search the help databasefor the <string> you specify and give you a list of likely commandsto look at with HELP.

-

11.48 init <node> (5) +

11.60 init <node> (5)

init <node> Re-initialise a link to an AK1A compatible node

This command attempts to re-initialise a link to a (usually) AK1A nodethat has got confused, usually by a protocol loop of some kind. It maywork - but you usually will be better off simply disconnecting it (orbetter, if it is a real AK1A node, doing an RCMD <node> DISC/F <yournode>).Best of luck - you will need it.

-

11.49 kill (5) +

11.61 kill (5)

kill

As a sysop you can kill any message on the system.

-

11.50 kill <from msgno>-<to msgno> (0) +

11.62 kill <from msgno>-<to msgno> (0)

kill <from msgno>-<to msgno> Delete a range of messages

-

11.51 kill <from>-<to> (5) +

11.63 kill <from>-<to> (5)

kill <from>-<to> Remove a range of messages from the system

-

11.52 kill <msgno> [<msgno..] (0) +

11.64 kill <msgno> [<msgno..] (0)

kill <msgno> [<msgno..] Delete a message from the local system

-

11.53 kill <msgno> [<msgno> ...] (0) +

11.65 kill <msgno> [<msgno> ...] (0)

kill <msgno> [<msgno> ...] Remove or erase a message from the system

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.

-

11.54 kill expunge <msgno> [<msgno..] (6) +

11.66 kill expunge <msgno> [<msgno..] (6)

kill expunge <msgno> [<msgno..] Expunge a message

Deleting a message using the normal KILL commands only marks that messagefor deletion. The actual deletion only happens later (usually two days later).The KILL EXPUNGE command causes the message to be truly deleted more or lessimmediately.It otherwise is used in the same way as the KILL command.

-

11.55 kill from <call> (5) +

11.67 kill from <call> (5)

kill from <call> Remove all messages from a callsign

-

11.56 kill full <msgno> [<msgno..] (5) +

11.68 kill full <msgno> [<msgno..] (5)

kill full <msgno> [<msgno..] Delete a message from the whole cluster

@@ -664,37 +802,67 @@ will delete all messages to g1tlh. will delete a message (usually a 'bulletin') from the whole cluster system. This uses the subject field, so any messages that have exactly thesame subject will be deleted. Beware!

-

11.57 kill full <msgno> [<msgno] (5) +

11.69 kill full <msgno> [<msgno] (5)

kill full <msgno> [<msgno] Remove a message from the entire cluster

Remove this message from the entire cluster system as well as your node.

-

11.58 kill to <call> (5) +

11.70 kill to <call> (5)

kill to <call> Remove all messages to a callsign

-

11.59 kill from <regex> (0) +

11.71 kill from <regex> (0)

kill from <regex> Delete messages FROM a callsign or pattern

-

11.60 kill to <regex> (0) +

11.72 kill to <regex> (0)

kill to <regex> Delete messages TO a callsign or pattern

-

11.61 links (0) +

11.73 links (0)

links Show which nodes is physically connected

This is a quick listing that shows which links are connected andsome information about them. See WHO for a list of all connections.

-

11.62 load/keps (5) +

11.74 load/aliases (9) +

+ +

load/aliases Reload the command alias table

+

Reload the /spider/cmd/Aliases file after you have editted it. Youwill need to do this if you change this file whilst the cluster isrunning in order for the changes to take effect.

+

11.75 load/badmsg (9) +

+ +

load/badmsg Reload the bad msg table

+

Reload the /spider/msg/badmsg.pl file if you have changed it manually whilstthe 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.

+

11.76 load/badwords (9) +

+ +

load/badwords Reload the bad words table

+

Reload the /spider/data/badwords file if you have changed it manually whilstthe cluster is running. This file contains a list of words which, if foundon certain text portions of PC protocol, will cause those protocol framesto be rejected. It will all put out a message if any of these words areused on the announce, dx and talk commands. The words can be one or more on a line, lines starting with '#' are ignored.

+

11.77 load/bands (9) +

+ +

load/bands Reload the band limits table

+

Reload the /spider/data/bands.pl file if you have changed it manually whilstthe cluster is running.

+

11.78 load/cmd_cache (9) +

+ +

load/cmd_cache Reload the automatic command cache

+

Normally, if you change a command file in the cmd or local_cmd tree itwill automatially be picked up by the cluster program. Sometimes itcan get confused if you are doing a lot of moving commands about ordelete a command in the local_cmd tree and want to use the normal oneagain. Execute this command to reset everything back to the state itwas just after a cluster restart.

+

11.79 load/forward (9) +

+ +

load/forward Reload the msg forwarding routing table

+

Reload the /spider/msg/forward.pl file if you have changed itmanually whilst the cluster is running.

+

11.80 load/keps (5)

load/keps Load new keps data

-

11.63 load/keps [nn] (5) +

11.81 load/keps [nn] (5)

load/keps [nn] Load new keps data from message

@@ -705,12 +873,39 @@ will delete a message (usually a 'bulletin') from the whole cluster system. This on a file containing NASA 2 line keps as a message issued by AMSAT. If there is a message number, then it will take the message, runconvkeps.pl on it and then load the data, all in one step.These messages are sent to ALL by GB7DJK (and others) from time to time.

-

11.64 merge <node> [<no spots>/<no wwv>] (5) +

11.82 load/messages (9) +

+ +

load/messages Reload the system messages file

+

If you change the /spider/perl/Messages file (usually whilstfiddling/writing new commands) you can have them take effect during acluster session by executing this command. You need to do this if getsomething like :-unknown message 'xxxx' in lang 'en'

+

11.83 load/prefixes (9) +

+ +

load/prefixes Reload the prefix table

+

Reload the /spider/data/prefix_data.pl file if you have changed itmanually whilst the cluster is running.

+

11.84 merge <node> [<no spots>/<no wwv>] (5)

merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV

MERGE allows you to bring your spot and wwv database up to date. By defaultit 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 appendedto your databases they will not duplicate any that have recently been added (the last 2 days for spots and last month for WWV data).

-

11.65 pc <call> <text> (8) +

11.85 msg <cmd> <msgno> [data ... ] (9) +

+ +

msg <cmd> <msgno> [data ... ] Alter various message parameters

+

Alter message parameters like To, From, Subject, whether private or bulletinor return receipt (RR) is required or whether to keep this message from timingout. +

+
+  MSG TO <msgno> <call>     - change TO callsign to <call>  MSG FRom <msgno> <call>   - change FROM callsign to <call>  MSG PRrivate <msgno>      - set private flag  MSG NOPRrivate <msgno>    - unset private flag  MSG RR <msgno>            - set RR flag  MSG NORR <msgno>          - unset RR flag  MSG KEep <msgno>          - set the keep flag (message won't be deleted ever)  MSG NOKEep <msgno>        - unset the keep flag  MSG SUbject <msgno> <new> - change the subject to <new>  MSG WAittime <msgno>      - remove any waitting time for this message  MSG NOREad <msgno>        - mark message as unread  MSG REad <msgno>          - mark message as read  MSG QUeue                 - queue any outstanding bulletins  MSG QUeue 1               - queue any outstanding private messages
+
+
+You can look at the status of a message by using:- +
+
+  STAT/MSG <msgno>      
+
+
+This will display more information on the message than DIR does.

+

11.86 pc <call> <text> (8)

pc <call> <text> Send arbitrary text to a connected callsign

@@ -727,37 +922,37 @@ or Send any text you like to the callsign requested. This is used mainly to sendPC protocol to connected nodes either for testing or to unstick things. You can also use in the same way as a talk command to a connected user butwithout any processing, added of "from <blah> to <blah" or whatever.

-

11.66 ping <node call> (1) +

11.87 ping <node call> (1)

ping <node call> Check the link quality between nodes

This command allows you to send a frame to another cluster node onthe network and get a return frame. The time it takes to do thisis a good indication of the quality of the link. The actual timeit takes is output to the console in seconds.Any visible cluster node can be PINGed.

-

11.67 rcmd <node call> <cmd> (1) +

11.88 rcmd <node call> <cmd> (1)

rcmd <node call> <cmd> Send a command to another DX Cluster

This command allows you to send nearly any command to another DX Clusternode that is connected to the system. Whether you get any output is dependant on a) whether the other system knowsthat the node callsign of this cluster is in fact a node b) whether theother system is allowing RCMDs from this node and c) whether you havepermission to send this command at all.

-

11.68 read (0) +

11.89 read (0)

read Read the next unread personal message addressed to you

-

11.69 read <msgno> (0) +

11.90 read <msgno> (0)

read <msgno> Read the specified message

You can read any messages that are sent as 'non-personal' and also anymessage either sent by or sent to your callsign.

-

11.70 read- (5) +

11.91 read- (5)

read-

As a sysop you may read any message on the system

-

11.71 reject (0) +

11.92 reject (0)

reject Set a filter to reject something

Create a filter to reject somethingThere are 2 types of filter, accept and reject. See HELP FILTERING for moreinfo.

-

11.72 reject/announce <call> [input] [0-9] <pattern> (8) +

11.93 reject/announce <call> [input] [0-9] <pattern> (8)

reject/announce <call> [input] [0-9] <pattern> Announce filter sysop version

@@ -768,7 +963,7 @@ Send any text you like to the callsign requested. This is used mainly to sendPC

-

11.73 reject/announce [0-9] <pattern> (0) +

11.94 reject/announce [0-9] <pattern> (0)

reject/announce [0-9] <pattern> Set a 'reject' filter line for announce

@@ -791,7 +986,7 @@ You can use the tag 'all' to reject everything eg: but this probably for advanced users...

-

11.74 reject/route <call> [0-9] <pattern> (8) +

11.95 reject/route <call> [0-9] <pattern> (8)

reject/route <call> [0-9] <pattern> Set an 'reject' filter line for routing

@@ -814,7 +1009,7 @@ You can use the tag 'all' to reject everything eg: as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.

-

11.75 reject/spots <call> [input] [0-9] <pattern> (8) +

11.96 reject/spots <call> [input] [0-9] <pattern> (8)

reject/spots <call> [input] [0-9] <pattern> Spot filter sysop version

@@ -830,7 +1025,7 @@ as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.

-

11.76 reject/spots [0-9] <pattern> (0) +

11.97 reject/spots [0-9] <pattern> (0)

reject/spots [0-9] <pattern> Set a 'reject' filter line for spots

@@ -853,7 +1048,7 @@ You can use the tag 'all' to reject everything eg: but this probably for advanced users...

-

11.77 reject/wcy <call> [input] [0-9] <pattern> (8) +

11.98 reject/wcy <call> [input] [0-9] <pattern> (8)

reject/wcy <call> [input] [0-9] <pattern> WCY filter sysop version

@@ -864,7 +1059,7 @@ but this probably for advanced users...

-

11.78 reject/wcy [0-9] <pattern> (0) +

11.99 reject/wcy [0-9] <pattern> (0)

reject/wcy [0-9] <pattern> set a 'reject' WCY filter

@@ -875,7 +1070,7 @@ but this probably for advanced users...

There are no examples because WCY Broadcasts only come from one place andyou 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.

-

11.79 reject/wwv <call> [input] [0-9] <pattern> (8) +

11.100 reject/wwv <call> [input] [0-9] <pattern> (8)

reject/wwv <call> [input] [0-9] <pattern> WWV filter sysop version

@@ -891,7 +1086,7 @@ There are no examples because WCY Broadcasts only come from one place andyou eit

-

11.80 reject/wwv [0-9] <pattern> (0) +

11.101 reject/wwv [0-9] <pattern> (0)

reject/wwv [0-9] <pattern> set a 'reject' WWV filter

@@ -908,42 +1103,77 @@ for example is probably the only useful thing to do (which will only show WWV broadcastsby stations in the US).See HELP FILTER for information.

-

11.81 reply (0) +

11.102 reply (0)

reply Reply (privately) to the last message that you have read

-

11.82 reply <msgno> (0) +

11.103 reply <msgno> (0)

reply <msgno> Reply (privately) to the specified message

-

11.83 reply b <msgno> (0) +

11.104 reply b <msgno> (0)

reply b <msgno> Reply as a Bulletin to the specified message

-

11.84 reply noprivate <msgno> (0) +

11.105 reply noprivate <msgno> (0)

reply noprivate <msgno> Reply as a Bulletin to the specified message

-

11.85 reply rr <msgno> (0) +

11.106 reply rr <msgno> (0)

reply rr <msgno> Reply to the specified message with read receipt

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 SENDfor further details)

-

11.86 send <call> [<call> ...] (0) +

11.107 save [-d -t -a] <filename> "<cmd>" [...] (9) +

+ +

save [-d -t -a] <filename> "<cmd>" [...] Save command output to a file

+

This sysop only cammand allows you to save the output of one or morecommands to a file. For example:- +

+
+  save /spider/packclus/dxstats show/dxstat
+
+
+will save the output of the normal command "show/dxstat" to the file"dxstats" in the files area.You can have some extra flags to the save which will either date stamp or time stamp or both the filename so:- +
+
+  save -d /tmp/a <cmd> creates /tmp/a_6-Jan-2002  save -t /tmp/a <cmd> creates /tmp/a_2301Z  save -d -t /tmp/a <cmd> creates /tmp/a_6-Jan-2002_2301Z
+
+
+The -a flag means append to the file instead of overwriting it.You can have more than one command on the line, to do this you MUSTenclose each command in double quotes (") eg:- +
+
+  save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
+
+
+or +
+
+  save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
+
+
+You can only write into places that the cluster has permission for (whichis that of the "sysop" user [which had BETTER NOT BE "root"]), you will need to create any directories you want to put stuff in beforehand as well.It is likely that you will want to run these commands in a crontab type situation. You would do that something like:- +
+
+  0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')
+
+
+Note that you still enclose each command with (") characters but you mustenclose the entire save command in (') characters. Now in fact, this can be varied if you know what you are doing. See theadmin manual for more details.

+

11.108 send <call> [<call> ...] (0)

send <call> [<call> ...] Send a message to one or more callsigns

-

11.87 send copy <msgno> <call> (0) +

11.109 send copy <msgno> <call> (0)

send copy <msgno> <call> Send a copy of a message to someone

-

11.88 send noprivate <call> (0) +

11.110 send noprivate <call> (0)

send noprivate <call> Send a message to all stations

@@ -978,112 +1208,117 @@ Will issue a dx annoucement to the rest of the cluster. Also, you can add the ou This will show YOU the output from SH/VHFTABLE and also store it in themessage. You can carry on with the message until you are ready to send it.

-

11.89 send private <call> (0) +

11.111 send private <call> (0)

send private <call> Send a personal message

-

11.90 send rr <call> (0) +

11.112 send rr <call> (0)

send rr <call> Send a message and ask for a read receipt

-

11.91 set/address <your address> (0) +

11.113 set/address <your address> (0)

set/address <your address> Record your postal address

-

11.92 set/announce (0) +

11.114 set/announce (0)

set/announce Allow announce messages to come out on your terminal

-

11.93 set/anntalk (0) +

11.115 set/anntalk (0)

set/anntalk Allow talk like announce messages on your terminal

-

11.94 set/arcluster <call> [<call>..] (5) +

11.116 set/arcluster <call> [<call>..] (5)

set/arcluster <call> [<call>..] Make the callsign an AR-Cluster node

-

11.95 set/baddx <call>.. (8) +

11.117 set/baddx <call>.. (8)

set/baddx <call>.. Stop callsigns in a dx spot being propagated

-

11.96 set/badnode <call>.. (8) +

11.118 set/badnode <call>.. (8)

set/badnode <call>.. Stop spots from this node being propagated

-

11.97 set/badspotter <call>.. (8) +

11.119 set/badspotter <call>.. (8)

set/badspotter <call>.. Stop spots from this callsign being propagated

-

11.98 set/badword <word>.. (8) +

11.120 set/badword <word>.. (8)

set/badword <word>.. Stop things with this word being propagated

-

11.99 set/bbs <call> [<call>..] (5) +

11.121 set/bbs <call> [<call>..] (5)

set/bbs <call> [<call>..] Make the callsign a BBS

-

11.100 set/beep (0) +

11.122 set/beep (0)

set/beep Add a beep to DX and other messages on your terminal

-

11.101 set/clx <call> [<call>..] (5) +

11.123 set/clx <call> [<call>..] (5)

set/clx <call> [<call>..] Make the callsign an CLX node

-

11.102 set/dx (0) +

11.124 set/debug <name> (9) +

+ +

set/debug <name> Add a debug level to the debug set

+ +

11.125 set/dx (0)

set/dx Allow DX messages to come out on your terminal

-

11.103 set/dxcq (0) +

11.126 set/dxcq (0)

set/dxcq Show CQ Zones on the end of DX announcements

-

11.104 set/dxgrid (0) +

11.127 set/dxgrid (0)

set/dxgrid Allow QRA Grid Squares on the end of DX announcements

-

11.105 set/dxitu (0) +

11.128 set/dxitu (0)

set/dxitu Show ITU Zones on the end of DX announcements

-

11.106 set/dxnet <call> [<call>..] (5) +

11.129 set/dxnet <call> [<call>..] (5)

set/dxnet <call> [<call>..] Make the callsign an DXNet node

-

11.107 set/echo (0) +

11.130 set/echo (0)

set/echo Make the cluster echo your input

-

11.108 set/email <email> ... (0) +

11.131 set/email <email> ... (0)

set/email <email> ... Set email address(es) and forward your personals

-

11.109 set/here (0) +

11.132 set/here (0)

set/here Tell the system you are present at your terminal

-

11.110 set/homenode <node> (0) +

11.133 set/homenode <node> (0)

set/homenode <node> Set your normal cluster callsign

@@ -1094,27 +1329,37 @@ This will show YOU the output from SH/VHFTABLE and also store it in themessage.

-

11.111 set/hops <call> ann|spots|route|wwv|wcy <n> (8) +

11.134 set/hops <call> ann|spots|route|wwv|wcy <n> (8)

set/hops <call> ann|spots|route|wwv|wcy <n> Set hop count

-

11.112 set/language <lang> (0) +

11.135 set/isolate (9) +

+ +

set/isolate Isolate a node from the rest of the network

+

Connect a node to your system in such a way that you are a full protocolmember of its network and can see all spots on it, but nothing either leaksout from it nor goes back into from the rest of the nodes connected to you.You can potentially connect several nodes in this way.

+

11.136 set/language <lang> (0)

set/language <lang> Set the language you want to use

You can select the language that you want the cluster to use. Currentlythe languages available are en (English), de (German), es (Spanish) and nl (Dutch).

-

11.113 set/location <lat & long> (0) +

11.137 set/location <lat & long> (0)

set/location <lat & long> Set your latitude and longitude

-

11.114 set/logininfo (0) +

11.138 set/lockout <call> (9) +

+ +

set/lockout <call> Stop a callsign connecting to the cluster

+ +

11.139 set/logininfo (0)

set/logininfo Inform when a station logs in locally

-

11.115 set/name <your name> (0) +

11.140 set/name <your name> (0)

set/name <your name> Set your name

@@ -1125,17 +1370,17 @@ This will show YOU the output from SH/VHFTABLE and also store it in themessage.

-

11.116 set/node <call> [<call>..] (5) +

11.141 set/node <call> [<call>..] (5)

set/node <call> [<call>..] Make the callsign an AK1A cluster

Tell the system that the call(s) are to be treated as AK1A cluster andfed PC Protocol rather normal user commands.

-

11.117 set/obscount <count> <call> (8) +

11.142 set/obscount <count> <call> (8)

set/obscount <count> <call> Set the 'pump-up' obscelence PING counter

From 1.35 onwards neighbouring nodes are pinged at regular intervals (seeSET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'counter which is decremented on every outgoing ping and then reset tothe 'obscount' value on every incoming ping. The default value of thisparameter 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 beforewhat would be the third attempt, that node is disconnected.If a ping is heard then the obscount is reset to the full value. Usingdefault values, if a node has not responded to a ping within 15 minutes,it is disconnected.You can set this parameter between 1 and 9.It is STRONGLY recommended that you don't change the default.

-

11.118 set/page <lines per page> (0) +

11.143 set/page <lines per page> (0)

set/page <lines per page> Set the lines per page

@@ -1146,17 +1391,50 @@ This will show YOU the output from SH/VHFTABLE and also store it in themessage. The setting is stored in your user profile.

-

11.119 set/password (0) +

11.144 set/password (0)

set/password Set your own password

This command only works for a 'telnet' user (currently). It willonly work if you have a password already set. This initial passwordcan 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 youget it right). You may or may not see the data echoed on the screenas you type, depending on the type of telnet client you have.

-

11.120 set/prompt <string> (0) +

11.145 set/password <callsign> <string> (9) +

+ +

set/password <callsign> <string> Set a users password

+

The password for a user can only be set by a full sysop. The stringcan contain any characters. The way this field is used depends on context. If it is being used inthe SYSOP command context then you are offered 5 random numbers and youhave to supply the corresponding letters. This is now mainly for ax25connections.If it is being used on incoming telnet connections then, if a passwordis set or the: +

+
+  set/var $main::passwdreq = 1
+
+
+command is executed in the startup script, then a password prompt isgiven after the normal 'login: ' prompt.

+

11.146 set/pinginterval <time> <nodecall> (9) +

+ +

set/pinginterval <time> <nodecall> Set ping time to neighbouring nodes

+

As from release 1.35 all neighbouring nodes are pinged at regular intervalsin order to determine the rolling quality of the link and, in future, toaffect 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 30 and secondsfor 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/OBSCOUNTfor more information.If you must change it (and it may be useful for internet connected nodeson dynamic IP addresses that go away after a set time of usage) the timecan be specified as:- +

+
+  5      which if less than 30 is converted to minutes otherwise is          taken as the no of seconds between pings.   120s   120 seconds  5m     5 minutes  1h     1 hour
+
+
+Please be aware that this causes traffic to occur on the link, setting this value too low may annoy your neighbours beyond the point of endurance!You can switch this off by setting it to 0.

+

11.147 set/privilege <n> <call> [<call..] (9) +

+ +

set/privilege <n> <call> [<call..] Set privilege level on a call

+

Set the privilege level on a callsign. The privilege levels that pertainto commands are as default:- +

+
+  0 - normal user  1 - allow remote nodes normal user RCMDs  5 - various privileged commands (including shutdown, but not disc-      connect), the normal level for another node.  8 - more privileged commands (including disconnect)  9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS      LEVEL.
+
+
+If you are a sysop and you come in as a normal user on a remote connectionyour privilege will automatically be set to 0.

+

11.148 set/prompt <string> (0)

set/prompt <string> Set your prompt to <string>

-

11.121 set/qra <locator> (0) +

11.149 set/qra <locator> (0)

set/qra <locator> Set your QRA Grid locator

@@ -1167,7 +1445,7 @@ The setting is stored in your user profile.

-

11.122 set/qth <your qth> (0) +

11.150 set/qth <your qth> (0)

set/qth <your qth> Set your QTH

@@ -1178,57 +1456,89 @@ The setting is stored in your user profile.

-

11.123 set/spider <call> [<call>..] (5) +

11.151 set/register <call> ... (9) +

+ +

set/register <call> ... Mark a user as registered

+ +

11.152 set/spider <call> [<call>..] (5)

set/spider <call> [<call>..] Make the callsign an DXSpider node

Tell the system that the call(s) are to be treated as DXSpider node andfed new style DX Protocol rather normal user commands.

-

11.124 set/talk (0) +

11.153 set/sys_location <lat & long> (9) +

+ +

set/sys_location <lat & long> Set your cluster latitude and longitude

+

In order to get accurate headings and such like you must tell the systemwhat your latitude and longitude is. If you have not yet done a SET/QRAthen this command will set your QRA locator for you. For example:- +

+
+  SET/LOCATION 52 22 N 0 57 E
+
+
+

+

11.154 set/sys_qra <locator> (9) +

+ +

set/sys_qra <locator> Set your cluster QRA Grid locator

+ +

11.155 set/talk (0)

set/talk Allow TALK messages to come out on your terminal

-

11.125 set/usstate (0) +

11.156 set/usdb <call> <state> <city> (9) +

+ +

set/usdb <call> <state> <city> add/update a US DB callsign

+

This command allows you to add or alter a callsign in the US statedatabase. Use with extreme caution. Anything you do here will beoverwritten by any weekly updates that affect this callsign +

+
+  set/usdb g1tlh nh downtown rindge
+
+
+see also DELETE/USDB

+

11.157 set/usstate (0)

set/usstate Allow US State info on the end of DX announcements

-

11.126 set/wcy (0) +

11.158 set/wcy (0)

set/wcy Allow WCY messages to come out on your terminal

-

11.127 set/wwv (0) +

11.159 set/wwv (0)

set/wwv Allow WWV messages to come out on your terminal

-

11.128 set/wx (0) +

11.160 set/wx (0)

set/wx Allow WX messages to come out on your terminal

-

11.129 show/baddx (1) +

11.161 show/baddx (1)

show/baddx Show all the bad dx calls in the system

Display all the bad dx callsigns in the system, see SET/BADDXfor more information.

-

11.130 show/badnode (1) +

11.162 show/badnode (1)

show/badnode Show all the bad nodes in the system

Display all the bad node callsigns in the system, see SET/BADNODEfor more information.

-

11.131 show/badspotter (1) +

11.163 show/badspotter (1)

show/badspotter Show all the bad spotters in the system

Display all the bad spotter's callsigns in the system, see SET/BADSPOTTERfor more information.

-

11.132 show/badword (1) +

11.164 show/badword (1)

show/badword Show all the bad words in the system

Display all the bad words in the system, see SET/BADWORDfor more information.

-

11.133 show/configuration [<node>] (0) +

11.165 show/configuration [<node>] (0)

show/configuration [<node>] Show all the nodes and users visible

@@ -1250,17 +1560,17 @@ will produce a complete list of all nodes. BE WARNED: the list that is returned

-

11.134 show/configuration/node (0) +

11.166 show/configuration/node (0)

show/configuration/node Show all the nodes connected locally

Show all the nodes connected to this node.

-

11.135 show/connect (1) +

11.167 show/connect (1)

show/connect Show all the active connections

This command shows information on all the active connections known tothe node. This command gives slightly more information than WHO.

-

11.136 show/contest <year and month> (0) +

11.168 show/contest <year and month> (0)

show/contest <year and month> Show all the contests for a month

@@ -1271,17 +1581,22 @@ will produce a complete list of all nodes. BE WARNED: the list that is returned

-

11.137 show/date [<prefix>|<callsign>] (0) +

11.169 show/date [<prefix>|<callsign>] (0)

show/date [<prefix>|<callsign>] Show the local time

This is very nearly the same as SHOW/TIME, the only difference the formatof the date string if no arguments are given.If no prefixes or callsigns are given then this command returns the localtime and UTC as the computer has it right now. If you give some prefixesthen it will show UTC and UTC + the local offset (not including DST) atthe prefixes or callsigns that you specify.

-

11.138 show/db0sdx <callsign> (0) +

11.170 show/db0sdx <callsign> (0)

show/db0sdx <callsign> Show QSL infomation from DB0SDX database

This command queries the DB0SDX QSL server on the internetand returns any information available for that callsign. This serviceis provided for users of this software by http://www.qslinfo.de.See also SHOW/QRZ, SHOW/WM7D.

-

11.139 show/dx (0) +

11.171 show/debug (9) +

+ +

show/debug Show what levels of debug information you are logging

+ +

11.172 show/dx (0)

show/dx Interrogate the spot database

@@ -1352,7 +1667,7 @@ will produce a complete list of all nodes. BE WARNED: the list that is returned

-

11.140 show/dxcc <prefix> (0) +

11.173 show/dxcc <prefix> (0)

show/dxcc <prefix> Interrogate the spot database by country

@@ -1369,7 +1684,7 @@ This can be done with the SHOW/DX command like this:-

-

11.141 show/dxqsl <callsign> (0) +

11.174 show/dxqsl <callsign> (0)

show/dxqsl <callsign> Show any QSL info gathered from spots

@@ -1386,12 +1701,12 @@ You can check the raw input spots yourself with:- This gives you more background information.

-

11.142 show/dxstats [days] [date] (0) +

11.175 show/dxstats [days] [date] (0)

show/dxstats [days] [date] Show the DX Statistics

Show the total DX spots for the last <days> no of days (default is 31), starting from a <date> (default: today).

-

11.143 show/files [<filearea> [<string>]] (0) +

11.176 show/files [<filearea> [<string>]] (0)

show/files [<filearea> [<string>]] List the contents of a filearea

@@ -1408,17 +1723,17 @@ where <filearea> is the name of the filearea you want to see the contents See also TYPE - to see the contents of a file.

-

11.144 show/filter (0) +

11.177 show/filter (0)

show/filter Show the contents of all the filters you have set

Show the contents of all the filters that are set. This command displaysall the filters set - for all the various categories.

-

11.145 show/hfstats [days] [date] (0) +

11.178 show/hfstats [days] [date] (0)

show/hfstats [days] [date] Show the HF DX Statistics

Show the HF DX spots breakdown by band for the last <days> no of days (default is 31), starting from a <date> (default: today).

-

11.146 show/hftable [days] [date] [prefix ...] (0) +

11.179 show/hftable [days] [date] [prefix ...] (0)

show/hftable [days] [date] [prefix ...] Show the HF DX Spotter Table

@@ -1447,22 +1762,27 @@ This will show the stats for your DXCC for that CQWW contest weekend. You can sp

-

11.147 show/hops <call> [ann|spots|route|wcy|wwv] (8) +

11.180 show/hops <call> [ann|spots|route|wcy|wwv] (8)

show/hops <call> [ann|spots|route|wcy|wwv] Show the hop counts for a node

This command shows the hop counts set up for a node. You can specifywhich category you want to see. If you leave the category out then all the categories will be listed.

-

11.148 show/isolate (1) +

11.181 show/isolate (1)

show/isolate Show list of ISOLATED nodes

-

11.149 show/log [<callsign>] (8) +

11.182 show/lockout <prefix>|all (9) +

+ +

show/lockout <prefix>|all Show the list of locked out or excluded callsigns

+ +

11.183 show/log [<callsign>] (8)

show/log [<callsign>] Show excerpts from the system log

This command outputs a short section of the system log. On its ownit will output a general logfile. With the optional callsign it willshow output from the log associated with that callsign.

-

11.150 show/moon [ndays] [<prefix>|<callsign>] (0) +

11.184 show/moon [ndays] [<prefix>|<callsign>] (0)

show/moon [ndays] [<prefix>|<callsign>] Show Moon rise and set times

@@ -1485,7 +1805,7 @@ or in three days time:- Upto 366 days can be checked both in the past and in the future.Please note that the rise and set times are given as the UT times of rise and set on the requested UT day.

-

11.151 show/muf <prefix> [<hours>][long] (0) +

11.185 show/muf <prefix> [<hours>][long] (0)

show/muf <prefix> [<hours>][long] Show the likely propagation to a prefix

@@ -1514,32 +1834,32 @@ will get you the above display, but with the next 24 hours worth ofpropagation d Gives you an estimate of the long path propagation characterics. Itshould be noted that the figures will probably not be very useful, norterrible accurate, but it is included for completeness.

-

11.152 show/newconfiguration [<node>] (0) +

11.186 show/newconfiguration [<node>] (0)

show/newconfiguration [<node>] Show all the nodes and users visible

This command allows you to see all the users that can be seenand the nodes to which they are connected. This command produces essentially the same information as SHOW/CONFIGURATION except that it shows all the duplication ofany routes that might be present It also uses a different formatwhich may not take up quite as much space if you don't have anyloops.BE WARNED: the list that is returned can be VERY long

-

11.153 show/newconfiguration/node (0) +

11.187 show/newconfiguration/node (0)

show/newconfiguration/node Show all the nodes connected locally

Show all the nodes connected to this node in the new format.

-

11.154 show/node [<callsign> ...] (1) +

11.188 show/node [<callsign> ...] (1)

show/node [<callsign> ...] Show the type and version number of nodes

Show the type and version (if connected) of the nodes specified on thecommand line. If no callsigns are specified then a sorted list of allthe non-user callsigns known to the system will be displayed.

-

11.155 show/prefix <callsign> (0) +

11.189 show/prefix <callsign> (0)

show/prefix <callsign> Interrogate the prefix database

This command takes the <callsign> (which can be a full or partial callsign or a prefix), looks up which internal country number it is and then displays all the relevant prefixes for that countrytogether with the internal country no, the CQ and ITU regions. See also SHOW/DXCC

-

11.156 show/program (5) +

11.190 show/program (5)

show/program Show the locations of all the included program modules

Show the name and location where every program module was load from. Thisis useful for checking where you think you have loaded a .pm file from.

-

11.157 show/qra <lat> <long> (0) +

11.191 show/qra <lat> <long> (0)

show/qra <lat> <long> Convert lat/long to a QRA Grid locator

@@ -1556,17 +1876,22 @@ The first example will show the distance and bearing to the locator fromyourself

-

11.158 show/qra <locator> [<locator>] (0) +

11.192 show/qra <locator> [<locator>] (0)

show/qra <locator> [<locator>] Show distance between QRA Grid locators

-

11.159 show/qrz <callsign> (0) +

11.193 show/qrz <callsign> (0)

show/qrz <callsign> Show any callbook details on a callsign

This command queries the QRZ callbook server on the internetand returns any information available for that callsign. This serviceis provided for users of this software by http://www.qrz.com See also SHOW/WM7D for an alternative.

-

11.160 show/route <callsign> ... (0) +

11.194 show/registered [<prefix>] (9) +

+ +

show/registered [<prefix>] Show the registered users

+ +

11.195 show/route <callsign> ... (0)

show/route <callsign> ... Show the route to the callsign

@@ -1577,7 +1902,7 @@ The first example will show the distance and bearing to the locator fromyourself

-

11.161 show/satellite <name> [<hours> <interval>] (0) +

11.196 show/satellite <name> [<hours> <interval>] (0)

show/satellite <name> [<hours> <interval>] Show tracking data

@@ -1588,12 +1913,12 @@ The first example will show the distance and bearing to the locator fromyourself

-

11.162 show/station all [<regex>] (6) +

11.197 show/station all [<regex>] (6)

show/station all [<regex>] Show list of users in the system

-

11.163 show/station [<callsign> ..] (0) +

11.198 show/station [<callsign> ..] (0)

show/station [<callsign> ..] Show information about a callsign

@@ -1604,7 +1929,7 @@ The first example will show the distance and bearing to the locator fromyourself If no callsign is given then show the information for yourself.

-

11.164 show/sun [ndays] [<prefix>|<callsign>] (0) +

11.199 show/sun [ndays] [<prefix>|<callsign>] (0)

show/sun [ndays] [<prefix>|<callsign>] Show sun rise and set times

@@ -1627,12 +1952,12 @@ or in three days time:- Upto 366 days can be checked both in the past and in the future.Please note that the rise and set times are given as the UT times of rise and set on the requested UT day.

-

11.165 show/time [<prefix>|<callsign>] (0) +

11.200 show/time [<prefix>|<callsign>] (0)

show/time [<prefix>|<callsign>] Show the local time

If no prefixes or callsigns are given then this command returns the localtime and UTC as the computer has it right now. If you give some prefixesthen it will show UTC and UTC + the local offset (not including DST) atthe prefixes or callsigns that you specify.

-

11.166 show/usdb [call ..] (0) +

11.201 show/usdb [call ..] (0)

show/usdb [call ..] Show information held on the FCC Call database

@@ -1643,12 +1968,12 @@ Upto 366 days can be checked both in the past and in the future.Please note that

-

11.167 show/vhfstats [days] [date] (0) +

11.202 show/vhfstats [days] [date] (0)

show/vhfstats [days] [date] Show the VHF DX Statistics

Show the VHF DX spots breakdown by band for the last <days> no of days (default is 31), starting from a date (default: today).

-

11.168 show/vhftable [days] [date] [prefix ...] (0) +

11.203 show/vhftable [days] [date] [prefix ...] (0)

show/vhftable [days] [date] [prefix ...] Show the VHF DX Spotter Table

@@ -1677,82 +2002,93 @@ This will show the stats for your DXCC for that CQWW contest weekend. You can sp

-

11.169 show/wcy (0) +

11.204 show/wcy (0)

show/wcy Show last 10 WCY broadcasts

-

11.170 show/wcy <n> (0) +

11.205 show/wcy <n> (0)

show/wcy <n> Show last <n> WCY broadcasts

Display the most recent WCY information that has been received by the system

-

11.171 show/wm7d <callsign> (0) +

11.206 show/wm7d <callsign> (0)

show/wm7d <callsign> Show callbook details on a US callsigns

This command queries the WM7D callbook server on the internetand returns any information available for that US callsign. This serviceis provided for users of this software by http://www.wm7d.net.See also SHOW/QRZ.

-

11.172 show/wwv (0) +

11.207 show/wwv (0)

show/wwv Show last 10 WWV broadcasts

-

11.173 show/wwv <n> (0) +

11.208 show/wwv <n> (0)

show/wwv <n> Show last <n> WWV broadcasts

Display the most recent WWV information that has been received by the system

-

11.174 shutdown (5) +

11.209 shutdown (5)

shutdown Shutdown the cluster

Shutdown the cluster and disconnect all the users

-

11.175 stat/channel [<callsign>] (5) +

11.210 spoof <call> <command> (9) +

+ +

spoof <call> <command> Do a command as though you are another user

+

This command is provided so that sysops can set a user's parameters withoutme having to write a special 'sysop' version for every user command. Itallows you to pretend that you are doing the command as the user you specify.eg:- +

+
+   SPOOF G1TLH set/name Dirk   SPOOF G1TLH set/qra JO02LQ
+
+
+

+

11.211 stat/channel [<callsign>] (5)

stat/channel [<callsign>] Show the status of a channel on the cluster

Show the internal status of the channel object either for the channel that you are on or else for the callsign that you asked for.Only the fields that are defined (in perl term) will be displayed.

-

11.176 stat/db <dbname> (5) +

11.212 stat/db <dbname> (5)

stat/db <dbname> Show the status of a database

Show the internal status of a database descriptor.Depending on your privilege level you will see more or less information. This command is unlikely to be of much use to anyone other than a sysop.

-

11.177 stat/msg (1) +

11.213 stat/msg (1)

stat/msg Show the status of the message system

-

11.178 stat/msg <msgno> (1) +

11.214 stat/msg <msgno> (1)

stat/msg <msgno> Show the status of a message

This command shows the internal status of a message and includes informationsuch as to whom it has been forwarded, its size, origin etc etc.If no message number is given then the status of the message system is displayed.

-

11.179 stat/route_node <callsign> (5) +

11.215 stat/route_node <callsign> (5)

stat/route_node <callsign> Show the data in a Route::Node object

-

11.180 stat/route_node all (5) +

11.216 stat/route_node all (5)

stat/route_node all Show list of all Route::Node objects

-

11.181 stat/route_user <callsign> (5) +

11.217 stat/route_user <callsign> (5)

stat/route_user <callsign> Show the data in a Route::User object

-

11.182 stat/route_user all (5) +

11.218 stat/route_user all (5)

stat/route_user all Show list of all Route::User objects

-

11.183 stat/user [<callsign>] (5) +

11.219 stat/user [<callsign>] (5)

stat/user [<callsign>] Show the full status of a user

Shows the full contents of a user record including all the secret flagsand stuff.Only the fields that are defined (in perl term) will be displayed.

-

11.184 sysop (0) +

11.220 sysop (0)

sysop Regain your privileges if you login remotely

@@ -1769,7 +2105,7 @@ you type:- They will all match. If there is no password you will still be offerednumbers but nothing will happen when you input a string. Any match iscase sensitive.

-

11.185 talk <call> > <node> [<text>] (0) +

11.221 talk <call> > <node> [<text>] (0)

talk <call> > <node> [<text>] Send a text message to another station via a node

@@ -1792,12 +2128,12 @@ If you are in 'Talk' mode, there is an extention to the '/' command whichallows will send the hftable as you have it to all the people you are currently talking to.

-

11.186 talk <call> [<text>] (0) +

11.222 talk <call> [<text>] (0)

talk <call> [<text>] Send a text message to another station

-

11.187 type <filearea>/<name> (0) +

11.223 type <filearea>/<name> (0)

type <filearea>/<name> Look at the contents of a file in one of the fileareas

@@ -1808,7 +2144,7 @@ will send the hftable as you have it to all the people you are currently talking See also SHOW/FILES to see what fileareas are available and a list of content.

-

11.188 uncatchup <node call> all|[msgno> ...] (5) +

11.224 uncatchup <node call> all|[msgno> ...] (5)

uncatchup <node call> all|[msgno> ...] Unmark a message as sent

@@ -1825,12 +2161,12 @@ and to undo what you have just done:- which will arrange for them to be forward candidates again.Order is not important.

-

11.189 unset/announce (0) +

11.225 unset/announce (0)

unset/announce Stop announce messages coming out on your terminal

-

11.190 unset/anntalk (0) +

11.226 unset/anntalk (0)

unset/anntalk Stop talk like announce messages on your terminal

@@ -1847,7 +2183,7 @@ you will suppress several of these announces, you may miss the odd useful one as allows you to see them again. This is the default.

-

11.191 unset/baddx <call>.. (8) +

11.227 unset/baddx <call>.. (8)

unset/baddx <call>.. Propagate a dx spot with this callsign again

@@ -1864,7 +2200,7 @@ To allow a word again, use the following command ...

-

11.192 unset/badnode <call>.. (8) +

11.228 unset/badnode <call>.. (8)

unset/badnode <call>.. Allow spots from this node again

@@ -1881,7 +2217,7 @@ will stop anything from K1TTT. If you want SSIDs as well then you mustenter them will allow spots from him again.Use with extreme care. This command may well be superceeded by FILTERing.

-

11.193 unset/badspotter <call>.. (8) +

11.229 unset/badspotter <call>.. (8)

unset/badspotter <call>.. Allow spots from this callsign again

@@ -1898,7 +2234,7 @@ will stop anything from VE2STN. This command will automaticallystop spots from t will allow spots from him again.Use with extreme care. This command may well be superceded by FILTERing.

-

11.194 unset/badword <word>.. (8) +

11.230 unset/badword <word>.. (8)

unset/badword <word>.. Propagate things with this word again

@@ -1915,37 +2251,48 @@ will stop anything with these words in the text. will allow text with this word again.

-

11.195 unset/beep (0) +

11.231 unset/beep (0)

unset/beep Stop beeps for DX and other messages on your terminal

-

11.196 unset/dx (0) +

11.232 unset/debug <name> (9) +

+ +

unset/debug <name> Remove a debug level from the debug set

+

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 SHOW/DEBUG

+

11.233 unset/dx (0)

unset/dx Stop DX messages coming out on your terminal

-

11.197 unset/dxcq (0) +

11.234 unset/dxcq (0)

unset/dxcq Stop CQ Zones on the end of DX announcements

Display both the Spotter's and the Spotted's CQ Zone on the endof a DX announcement (there is just enough room). Some user programscannot cope with this. The Spotter's CQ is on the RHS of the time, the Spotted's CQ is on the LHS.Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATEDo a STAT/USER to see which flags you have set if you are confused.

-

11.198 unset/dxgrid (0) +

11.235 unset/dxgrid (0)

unset/dxgrid Stop QRA Grid Squares on the end of DX announcements

A standard feature which is enabled in version 1.43 and above is that if the spotter's grid square is known it is output on the endof a DX announcement (there is just enough room). Some user programscannot cope with this. You can use this command to reset (or set)this feature.Conflicts with: SET/DXCQ, SET/DXITUDo a STAT/USER to see which flags you have set if you are confused.

-

11.199 unset/dxitu (0) +

11.236 unset/dxitu (0)

unset/dxitu Stop ITU Zones on the end of DX announcements

Display both the Spotter's and the Spotted's ITU Zone on the endof a DX announcement (there is just enough room). Some user programscannot cope with this. The Spotter's ITU is on the RHS of the time, the Spotted's ITU is on the LHS.Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATEDo a STAT/USER to see which flags you have set if you are confused.

-

11.200 unset/echo (0) +

11.237 unset/echo (0)

unset/echo Stop the cluster echoing your input

If you are connected via a telnet session, different implimentationsof telnet handle echo differently depending on whether you are connected via port 23 or some other port. You can use this commandto change the setting appropriately. The setting is stored in your user profile.YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.

-

11.201 unset/email (0) +

11.238 unset/email (0)

unset/email Stop personal msgs being forwarded by email

@@ -1962,12 +2309,12 @@ You can have more than one email address (each one separated by a space).Emails

-

11.202 unset/here (0) +

11.239 unset/here (0)

unset/here Tell the system you are absent from your terminal

-

11.203 unset/hops <call> ann|spots|route|wwv|wcy (8) +

11.240 unset/hops <call> ann|spots|route|wwv|wcy (8)

unset/hops <call> ann|spots|route|wwv|wcy Unset hop count

@@ -1984,17 +2331,32 @@ Set SHOW/HOPS for information on what is already set. This commandcreates a filt

-

11.204 unset/logininfo (0) +

11.241 unset/isolate (9) +

+ +

unset/isolate Stop Isolation of a node from the rest of the network

+

Remove isolation from a node - SET/ISOLATE

+

11.242 unset/lockout <call> (9) +

+ +

unset/lockout <call> Allow a callsign to connect to the cluster

+ +

11.243 unset/logininfo (0)

unset/logininfo Inform when a station logs out locally

-

11.205 unset/privilege (0) +

11.244 unset/password <call> ... (9) +

+ +

unset/password <call> ... Delete (remove) a user's password

+

This command allows the sysop to completely delete and remove a password for a user.

+

11.245 unset/privilege (0)

unset/privilege Remove any privilege for this session

You can use this command to 'protect' this session from unauthoriseduse. If you want to get your normal privilege back you will need toeither logout and login again (if you are on a console) or use theSYSOP command.

-

11.206 unset/prompt (0) +

11.246 unset/prompt (0)

unset/prompt Set your prompt back to default

@@ -2005,47 +2367,58 @@ Set SHOW/HOPS for information on what is already set. This commandcreates a filt UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back tonormal.

-

11.207 unset/talk (0) +

11.247 unset/register <call> ... (9) +

+ +

unset/register <call> ... Mark a user as not registered

+

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 normalmotd file (/spider/data/motd) being sent to the user at startup, theuser is sent the motd_nor file instead. Secondly, the non registereduser only has READ-ONLY access to the node. The non-registered usercannot use DX, ANN etc. The only exception to this is that a non-registered user can TALK orSEND messages to the sysop.

+

11.248 unset/talk (0)

unset/talk Stop TALK messages coming out on your terminal

-

11.208 unset/usstate (0) +

11.249 unset/usstate (0)

unset/usstate Stop US State info on the end of DX announcements

If the spotter's or spotted's US State is known it is output on the end of a DX announcement (there is just enough room). A spotter's state will appear on the RHS of the time (like SET/DXGRID) and the spotted's State will appear on the LHS of thetime field. Any information found will override any locator information from SET/DXGRID.Some user programs cannot cope with this. You can use this command to reset (or set) this feature.Conflicts with: SET/DXCQ, SET/DXITUDo a STAT/USER to see which flags you have set if you are confused.

-

11.209 unset/wcy (0) +

11.250 unset/wcy (0)

unset/wcy Stop WCY messages coming out on your terminal

-

11.210 unset/wwv (0) +

11.251 unset/wwv (0)

unset/wwv Stop WWV messages coming out on your terminal

-

11.211 unset/wx (0) +

11.252 unset/wx (0)

unset/wx Stop WX messages coming out on your terminal

-

11.212 who (0) +

11.253 who (0)

who Show who is physically connected

This is a quick listing that shows which callsigns are connected andwhat sort of connection they have

-

11.213 wx <text> (0) +

11.254 wx <text> (0)

wx <text> Send a weather message to local users

-

11.214 wx full <text> (0) +

11.255 wx full <text> (0)

wx full <text> Send a weather message to all cluster users

-

11.215 wx sysop <text> (5) +

11.256 wx sysop <text> (5)

wx sysop <text> Send a weather message to other clusters only

diff --git a/html/adminmanual_en.html b/html/adminmanual_en.html index 750f0b88..367aec3b 100644 --- a/html/adminmanual_en.html +++ b/html/adminmanual_en.html @@ -138,192 +138,233 @@ Charlie Carroll, K1XX, (k1xx@ptcnh.net)March 2003 revision 0.5
  • 11.27 clear/wwv [1|all] (0)
  • 11.28 connect <callsign> (5)
  • 11.29 dbavail (0) -
  • 11.30 dbshow <dbname> <key> (0) -
  • 11.31 directory (0) -
  • 11.32 directory <from>-<to> (0) -
  • 11.33 directory <nn> (0) -
  • 11.34 directory all (0) -
  • 11.35 directory from <call> (0) -
  • 11.36 directory new (0) -
  • 11.37 directory own (0) -
  • 11.38 directory subject <string> (0) -
  • 11.39 directory to <call> (0) -
  • 11.40 directory- (5) -
  • 11.41 disconnect <call> [<call> ...] (8) -
  • 11.42 dx [by <call>] <freq> <call> <remarks> (0) -
  • 11.43 echo <line> (0) -
  • 11.44 filtering... (0) -
  • 11.45 forward/latlong <node_call> (8) -
  • 11.46 forward/opernam <call> (1) -
  • 11.47 help (0) -
  • 11.48 init <node> (5) -
  • 11.49 kill (5) -
  • 11.50 kill <from msgno>-<to msgno> (0) -
  • 11.51 kill <from>-<to> (5) -
  • 11.52 kill <msgno> [<msgno..] (0) -
  • 11.53 kill <msgno> [<msgno> ...] (0) -
  • 11.54 kill expunge <msgno> [<msgno..] (6) -
  • 11.55 kill from <call> (5) -
  • 11.56 kill full <msgno> [<msgno..] (5) -
  • 11.57 kill full <msgno> [<msgno] (5) -
  • 11.58 kill to <call> (5) -
  • 11.59 kill from <regex> (0) -
  • 11.60 kill to <regex> (0) -
  • 11.61 links (0) -
  • 11.62 load/keps (5) -
  • 11.63 load/keps [nn] (5) -
  • 11.64 merge <node> [<no spots>/<no wwv>] (5) -
  • 11.65 pc <call> <text> (8) -
  • 11.66 ping <node call> (1) -
  • 11.67 rcmd <node call> <cmd> (1) -
  • 11.68 read (0) -
  • 11.69 read <msgno> (0) -
  • 11.70 read- (5) -
  • 11.71 reject (0) -
  • 11.72 reject/announce <call> [input] [0-9] <pattern> (8) -
  • 11.73 reject/announce [0-9] <pattern> (0) -
  • 11.74 reject/route <call> [0-9] <pattern> (8) -
  • 11.75 reject/spots <call> [input] [0-9] <pattern> (8) -
  • 11.76 reject/spots [0-9] <pattern> (0) -
  • 11.77 reject/wcy <call> [input] [0-9] <pattern> (8) -
  • 11.78 reject/wcy [0-9] <pattern> (0) -
  • 11.79 reject/wwv <call> [input] [0-9] <pattern> (8) -
  • 11.80 reject/wwv [0-9] <pattern> (0) -
  • 11.81 reply (0) -
  • 11.82 reply <msgno> (0) -
  • 11.83 reply b <msgno> (0) -
  • 11.84 reply noprivate <msgno> (0) -
  • 11.85 reply rr <msgno> (0) -
  • 11.86 send <call> [<call> ...] (0) -
  • 11.87 send copy <msgno> <call> (0) -
  • 11.88 send noprivate <call> (0) -
  • 11.89 send private <call> (0) -
  • 11.90 send rr <call> (0) -
  • 11.91 set/address <your address> (0) -
  • 11.92 set/announce (0) -
  • 11.93 set/anntalk (0) -
  • 11.94 set/arcluster <call> [<call>..] (5) -
  • 11.95 set/baddx <call>.. (8) -
  • 11.96 set/badnode <call>.. (8) -
  • 11.97 set/badspotter <call>.. (8) -
  • 11.98 set/badword <word>.. (8) -
  • 11.99 set/bbs <call> [<call>..] (5) -
  • 11.100 set/beep (0) -
  • 11.101 set/clx <call> [<call>..] (5) -
  • 11.102 set/dx (0) -
  • 11.103 set/dxcq (0) -
  • 11.104 set/dxgrid (0) -
  • 11.105 set/dxitu (0) -
  • 11.106 set/dxnet <call> [<call>..] (5) -
  • 11.107 set/echo (0) -
  • 11.108 set/email <email> ... (0) -
  • 11.109 set/here (0) -
  • 11.110 set/homenode <node> (0) -
  • 11.111 set/hops <call> ann|spots|route|wwv|wcy <n> (8) -
  • 11.112 set/language <lang> (0) -
  • 11.113 set/location <lat & long> (0) -
  • 11.114 set/logininfo (0) -
  • 11.115 set/name <your name> (0) -
  • 11.116 set/node <call> [<call>..] (5) -
  • 11.117 set/obscount <count> <call> (8) -
  • 11.118 set/page <lines per page> (0) -
  • 11.119 set/password (0) -
  • 11.120 set/prompt <string> (0) -
  • 11.121 set/qra <locator> (0) -
  • 11.122 set/qth <your qth> (0) -
  • 11.123 set/spider <call> [<call>..] (5) -
  • 11.124 set/talk (0) -
  • 11.125 set/usstate (0) -
  • 11.126 set/wcy (0) -
  • 11.127 set/wwv (0) -
  • 11.128 set/wx (0) -
  • 11.129 show/baddx (1) -
  • 11.130 show/badnode (1) -
  • 11.131 show/badspotter (1) -
  • 11.132 show/badword (1) -
  • 11.133 show/configuration [<node>] (0) -
  • 11.134 show/configuration/node (0) -
  • 11.135 show/connect (1) -
  • 11.136 show/contest <year and month> (0) -
  • 11.137 show/date [<prefix>|<callsign>] (0) -
  • 11.138 show/db0sdx <callsign> (0) -
  • 11.139 show/dx (0) -
  • 11.140 show/dxcc <prefix> (0) -
  • 11.141 show/dxqsl <callsign> (0) -
  • 11.142 show/dxstats [days] [date] (0) -
  • 11.143 show/files [<filearea> [<string>]] (0) -
  • 11.144 show/filter (0) -
  • 11.145 show/hfstats [days] [date] (0) -
  • 11.146 show/hftable [days] [date] [prefix ...] (0) -
  • 11.147 show/hops <call> [ann|spots|route|wcy|wwv] (8) -
  • 11.148 show/isolate (1) -
  • 11.149 show/log [<callsign>] (8) -
  • 11.150 show/moon [ndays] [<prefix>|<callsign>] (0) -
  • 11.151 show/muf <prefix> [<hours>][long] (0) -
  • 11.152 show/newconfiguration [<node>] (0) -
  • 11.153 show/newconfiguration/node (0) -
  • 11.154 show/node [<callsign> ...] (1) -
  • 11.155 show/prefix <callsign> (0) -
  • 11.156 show/program (5) -
  • 11.157 show/qra <lat> <long> (0) -
  • 11.158 show/qra <locator> [<locator>] (0) -
  • 11.159 show/qrz <callsign> (0) -
  • 11.160 show/route <callsign> ... (0) -
  • 11.161 show/satellite <name> [<hours> <interval>] (0) -
  • 11.162 show/station all [<regex>] (6) -
  • 11.163 show/station [<callsign> ..] (0) -
  • 11.164 show/sun [ndays] [<prefix>|<callsign>] (0) -
  • 11.165 show/time [<prefix>|<callsign>] (0) -
  • 11.166 show/usdb [call ..] (0) -
  • 11.167 show/vhfstats [days] [date] (0) -
  • 11.168 show/vhftable [days] [date] [prefix ...] (0) -
  • 11.169 show/wcy (0) -
  • 11.170 show/wcy <n> (0) -
  • 11.171 show/wm7d <callsign> (0) -
  • 11.172 show/wwv (0) -
  • 11.173 show/wwv <n> (0) -
  • 11.174 shutdown (5) -
  • 11.175 stat/channel [<callsign>] (5) -
  • 11.176 stat/db <dbname> (5) -
  • 11.177 stat/msg (1) -
  • 11.178 stat/msg <msgno> (1) -
  • 11.179 stat/route_node <callsign> (5) -
  • 11.180 stat/route_node all (5) -
  • 11.181 stat/route_user <callsign> (5) -
  • 11.182 stat/route_user all (5) -
  • 11.183 stat/user [<callsign>] (5) -
  • 11.184 sysop (0) -
  • 11.185 talk <call> > <node> [<text>] (0) -
  • 11.186 talk <call> [<text>] (0) -
  • 11.187 type <filearea>/<name> (0) -
  • 11.188 uncatchup <node call> all|[msgno> ...] (5) -
  • 11.189 unset/announce (0) -
  • 11.190 unset/anntalk (0) -
  • 11.191 unset/baddx <call>.. (8) -
  • 11.192 unset/badnode <call>.. (8) -
  • 11.193 unset/badspotter <call>.. (8) -
  • 11.194 unset/badword <word>.. (8) -
  • 11.195 unset/beep (0) -
  • 11.196 unset/dx (0) -
  • 11.197 unset/dxcq (0) -
  • 11.198 unset/dxgrid (0) -
  • 11.199 unset/dxitu (0) -
  • 11.200 unset/echo (0) -
  • 11.201 unset/email (0) -
  • 11.202 unset/here (0) -
  • 11.203 unset/hops <call> ann|spots|route|wwv|wcy (8) -
  • 11.204 unset/logininfo (0) -
  • 11.205 unset/privilege (0) -
  • 11.206 unset/prompt (0) -
  • 11.207 unset/talk (0) -
  • 11.208 unset/usstate (0) -
  • 11.209 unset/wcy (0) -
  • 11.210 unset/wwv (0) -
  • 11.211 unset/wx (0) -
  • 11.212 who (0) -
  • 11.213 wx <text> (0) -
  • 11.214 wx full <text> (0) -
  • 11.215 wx sysop <text> (5) +
  • 11.30 dbcreate <name> (9) +
  • 11.31 dbcreate <name> chain <name> [<name>..] (9) +
  • 11.32 dbcreate <name> cmd <dxspider command> (9) +
  • 11.33 dbcreate <name> remote <node> (9) +
  • 11.34 dbimport <dbname> <filename> (9) +
  • 11.35 dbremove <dbname> (9) +
  • 11.36 dbshow <dbname> <key> (0) +
  • 11.37 debug (9) +
  • 11.38 delete/usdb <callsign> ... (9) +
  • 11.39 delete/user <callsign> ... (9) +
  • 11.40 demonstrate <call> <command> (9) +
  • 11.41 directory (0) +
  • 11.42 directory <from>-<to> (0) +
  • 11.43 directory <nn> (0) +
  • 11.44 directory all (0) +
  • 11.45 directory from <call> (0) +
  • 11.46 directory new (0) +
  • 11.47 directory own (0) +
  • 11.48 directory subject <string> (0) +
  • 11.49 directory to <call> (0) +
  • 11.50 directory- (5) +
  • 11.51 disconnect <call> [<call> ...] (8) +
  • 11.52 dx [by <call>] <freq> <call> <remarks> (0) +
  • 11.53 echo <line> (0) +
  • 11.54 export <msgno> <filename> (9) +
  • 11.55 export_users [<filename>] (9) +
  • 11.56 filtering... (0) +
  • 11.57 forward/latlong <node_call> (8) +
  • 11.58 forward/opernam <call> (1) +
  • 11.59 help (0) +
  • 11.60 init <node> (5) +
  • 11.61 kill (5) +
  • 11.62 kill <from msgno>-<to msgno> (0) +
  • 11.63 kill <from>-<to> (5) +
  • 11.64 kill <msgno> [<msgno..] (0) +
  • 11.65 kill <msgno> [<msgno> ...] (0) +
  • 11.66 kill expunge <msgno> [<msgno..] (6) +
  • 11.67 kill from <call> (5) +
  • 11.68 kill full <msgno> [<msgno..] (5) +
  • 11.69 kill full <msgno> [<msgno] (5) +
  • 11.70 kill to <call> (5) +
  • 11.71 kill from <regex> (0) +
  • 11.72 kill to <regex> (0) +
  • 11.73 links (0) +
  • 11.74 load/aliases (9) +
  • 11.75 load/badmsg (9) +
  • 11.76 load/badwords (9) +
  • 11.77 load/bands (9) +
  • 11.78 load/cmd_cache (9) +
  • 11.79 load/forward (9) +
  • 11.80 load/keps (5) +
  • 11.81 load/keps [nn] (5) +
  • 11.82 load/messages (9) +
  • 11.83 load/prefixes (9) +
  • 11.84 merge <node> [<no spots>/<no wwv>] (5) +
  • 11.85 msg <cmd> <msgno> [data ... ] (9) +
  • 11.86 pc <call> <text> (8) +
  • 11.87 ping <node call> (1) +
  • 11.88 rcmd <node call> <cmd> (1) +
  • 11.89 read (0) +
  • 11.90 read <msgno> (0) +
  • 11.91 read- (5) +
  • 11.92 reject (0) +
  • 11.93 reject/announce <call> [input] [0-9] <pattern> (8) +
  • 11.94 reject/announce [0-9] <pattern> (0) +
  • 11.95 reject/route <call> [0-9] <pattern> (8) +
  • 11.96 reject/spots <call> [input] [0-9] <pattern> (8) +
  • 11.97 reject/spots [0-9] <pattern> (0) +
  • 11.98 reject/wcy <call> [input] [0-9] <pattern> (8) +
  • 11.99 reject/wcy [0-9] <pattern> (0) +
  • 11.100 reject/wwv <call> [input] [0-9] <pattern> (8) +
  • 11.101 reject/wwv [0-9] <pattern> (0) +
  • 11.102 reply (0) +
  • 11.103 reply <msgno> (0) +
  • 11.104 reply b <msgno> (0) +
  • 11.105 reply noprivate <msgno> (0) +
  • 11.106 reply rr <msgno> (0) +
  • 11.107 save [-d -t -a] <filename> "<cmd>" [...] (9) +
  • 11.108 send <call> [<call> ...] (0) +
  • 11.109 send copy <msgno> <call> (0) +
  • 11.110 send noprivate <call> (0) +
  • 11.111 send private <call> (0) +
  • 11.112 send rr <call> (0) +
  • 11.113 set/address <your address> (0) +
  • 11.114 set/announce (0) +
  • 11.115 set/anntalk (0) +
  • 11.116 set/arcluster <call> [<call>..] (5) +
  • 11.117 set/baddx <call>.. (8) +
  • 11.118 set/badnode <call>.. (8) +
  • 11.119 set/badspotter <call>.. (8) +
  • 11.120 set/badword <word>.. (8) +
  • 11.121 set/bbs <call> [<call>..] (5) +
  • 11.122 set/beep (0) +
  • 11.123 set/clx <call> [<call>..] (5) +
  • 11.124 set/debug <name> (9) +
  • 11.125 set/dx (0) +
  • 11.126 set/dxcq (0) +
  • 11.127 set/dxgrid (0) +
  • 11.128 set/dxitu (0) +
  • 11.129 set/dxnet <call> [<call>..] (5) +
  • 11.130 set/echo (0) +
  • 11.131 set/email <email> ... (0) +
  • 11.132 set/here (0) +
  • 11.133 set/homenode <node> (0) +
  • 11.134 set/hops <call> ann|spots|route|wwv|wcy <n> (8) +
  • 11.135 set/isolate (9) +
  • 11.136 set/language <lang> (0) +
  • 11.137 set/location <lat & long> (0) +
  • 11.138 set/lockout <call> (9) +
  • 11.139 set/logininfo (0) +
  • 11.140 set/name <your name> (0) +
  • 11.141 set/node <call> [<call>..] (5) +
  • 11.142 set/obscount <count> <call> (8) +
  • 11.143 set/page <lines per page> (0) +
  • 11.144 set/password (0) +
  • 11.145 set/password <callsign> <string> (9) +
  • 11.146 set/pinginterval <time> <nodecall> (9) +
  • 11.147 set/privilege <n> <call> [<call..] (9) +
  • 11.148 set/prompt <string> (0) +
  • 11.149 set/qra <locator> (0) +
  • 11.150 set/qth <your qth> (0) +
  • 11.151 set/register <call> ... (9) +
  • 11.152 set/spider <call> [<call>..] (5) +
  • 11.153 set/sys_location <lat & long> (9) +
  • 11.154 set/sys_qra <locator> (9) +
  • 11.155 set/talk (0) +
  • 11.156 set/usdb <call> <state> <city> (9) +
  • 11.157 set/usstate (0) +
  • 11.158 set/wcy (0) +
  • 11.159 set/wwv (0) +
  • 11.160 set/wx (0) +
  • 11.161 show/baddx (1) +
  • 11.162 show/badnode (1) +
  • 11.163 show/badspotter (1) +
  • 11.164 show/badword (1) +
  • 11.165 show/configuration [<node>] (0) +
  • 11.166 show/configuration/node (0) +
  • 11.167 show/connect (1) +
  • 11.168 show/contest <year and month> (0) +
  • 11.169 show/date [<prefix>|<callsign>] (0) +
  • 11.170 show/db0sdx <callsign> (0) +
  • 11.171 show/debug (9) +
  • 11.172 show/dx (0) +
  • 11.173 show/dxcc <prefix> (0) +
  • 11.174 show/dxqsl <callsign> (0) +
  • 11.175 show/dxstats [days] [date] (0) +
  • 11.176 show/files [<filearea> [<string>]] (0) +
  • 11.177 show/filter (0) +
  • 11.178 show/hfstats [days] [date] (0) +
  • 11.179 show/hftable [days] [date] [prefix ...] (0) +
  • 11.180 show/hops <call> [ann|spots|route|wcy|wwv] (8) +
  • 11.181 show/isolate (1) +
  • 11.182 show/lockout <prefix>|all (9) +
  • 11.183 show/log [<callsign>] (8) +
  • 11.184 show/moon [ndays] [<prefix>|<callsign>] (0) +
  • 11.185 show/muf <prefix> [<hours>][long] (0) +
  • 11.186 show/newconfiguration [<node>] (0) +
  • 11.187 show/newconfiguration/node (0) +
  • 11.188 show/node [<callsign> ...] (1) +
  • 11.189 show/prefix <callsign> (0) +
  • 11.190 show/program (5) +
  • 11.191 show/qra <lat> <long> (0) +
  • 11.192 show/qra <locator> [<locator>] (0) +
  • 11.193 show/qrz <callsign> (0) +
  • 11.194 show/registered [<prefix>] (9) +
  • 11.195 show/route <callsign> ... (0) +
  • 11.196 show/satellite <name> [<hours> <interval>] (0) +
  • 11.197 show/station all [<regex>] (6) +
  • 11.198 show/station [<callsign> ..] (0) +
  • 11.199 show/sun [ndays] [<prefix>|<callsign>] (0) +
  • 11.200 show/time [<prefix>|<callsign>] (0) +
  • 11.201 show/usdb [call ..] (0) +
  • 11.202 show/vhfstats [days] [date] (0) +
  • 11.203 show/vhftable [days] [date] [prefix ...] (0) +
  • 11.204 show/wcy (0) +
  • 11.205 show/wcy <n> (0) +
  • 11.206 show/wm7d <callsign> (0) +
  • 11.207 show/wwv (0) +
  • 11.208 show/wwv <n> (0) +
  • 11.209 shutdown (5) +
  • 11.210 spoof <call> <command> (9) +
  • 11.211 stat/channel [<callsign>] (5) +
  • 11.212 stat/db <dbname> (5) +
  • 11.213 stat/msg (1) +
  • 11.214 stat/msg <msgno> (1) +
  • 11.215 stat/route_node <callsign> (5) +
  • 11.216 stat/route_node all (5) +
  • 11.217 stat/route_user <callsign> (5) +
  • 11.218 stat/route_user all (5) +
  • 11.219 stat/user [<callsign>] (5) +
  • 11.220 sysop (0) +
  • 11.221 talk <call> > <node> [<text>] (0) +
  • 11.222 talk <call> [<text>] (0) +
  • 11.223 type <filearea>/<name> (0) +
  • 11.224 uncatchup <node call> all|[msgno> ...] (5) +
  • 11.225 unset/announce (0) +
  • 11.226 unset/anntalk (0) +
  • 11.227 unset/baddx <call>.. (8) +
  • 11.228 unset/badnode <call>.. (8) +
  • 11.229 unset/badspotter <call>.. (8) +
  • 11.230 unset/badword <word>.. (8) +
  • 11.231 unset/beep (0) +
  • 11.232 unset/debug <name> (9) +
  • 11.233 unset/dx (0) +
  • 11.234 unset/dxcq (0) +
  • 11.235 unset/dxgrid (0) +
  • 11.236 unset/dxitu (0) +
  • 11.237 unset/echo (0) +
  • 11.238 unset/email (0) +
  • 11.239 unset/here (0) +
  • 11.240 unset/hops <call> ann|spots|route|wwv|wcy (8) +
  • 11.241 unset/isolate (9) +
  • 11.242 unset/lockout <call> (9) +
  • 11.243 unset/logininfo (0) +
  • 11.244 unset/password <call> ... (9) +
  • 11.245 unset/privilege (0) +
  • 11.246 unset/prompt (0) +
  • 11.247 unset/register <call> ... (9) +
  • 11.248 unset/talk (0) +
  • 11.249 unset/usstate (0) +
  • 11.250 unset/wcy (0) +
  • 11.251 unset/wwv (0) +
  • 11.252 unset/wx (0) +
  • 11.253 who (0) +
  • 11.254 wx <text> (0) +
  • 11.255 wx full <text> (0) +
  • 11.256 wx sysop <text> (5)
    Next diff --git a/html/installation_en-7.html b/html/installation_en-7.html index b2311b5e..7e4bda1a 100644 --- a/html/installation_en-7.html +++ b/html/installation_en-7.html @@ -40,7 +40,7 @@ then a connect attempt will be started.

    There are probably lots of other things you could use this crontab file for. If you want to know more about it, look at the -DXSpider website +DXSpider website at the cron page where it is explained more fully.

    diff --git a/html/installation_en.html b/html/installation_en.html index 83c86557..3f1ead27 100644 --- a/html/installation_en.html +++ b/html/installation_en.html @@ -17,7 +17,7 @@ Contents

    Iain Philipps, G0RDI (g0rdi@77hz.com), Ian Maude, G0VGS, (g0vgs@gb7mbc.net) and Charlie -Carroll, K1XX, (k1xx@ptcnh.net)

    February 2003 revision 0.6 +Carroll, K1XX, (k1xx@ptcnh.net)March 2003 revision 0.7
    A reference for SysOps of the DXSpider DXCluster program.
    diff --git a/sgml/Makefile b/sgml/Makefile index 1056584a..8ef3b321 100644 --- a/sgml/Makefile +++ b/sgml/Makefile @@ -6,7 +6,7 @@ all: sgml ../html/adminmanual.html ../txt/adminmanual.txt ../html/installation.h sgml: ../cmd/Commands_en.hlp adminmanual.sgml usermanual.sgml # Create the admin manual sgml file - cat ../cmd/Commands_en.hlp | ./commands2sgml.pl 8 > ./adminmanual-cmd.sgml + cat ../cmd/Commands_en.hlp | ./commands2sgml.pl 9 > ./adminmanual-cmd.sgml cat adminmanual.sgml adminmanual-cmd.sgml > ./adminmanual_en.sgml # Create the user manual sgml file diff --git a/sgml/adminmanual_en.sgml b/sgml/adminmanual_en.sgml index 9f802770..5b571eb2 100644 --- a/sgml/adminmanual_en.sgml +++ b/sgml/adminmanual_en.sgml @@ -2376,6 +2376,164 @@ necessary to traverse the network(s) to logon to the cluster <callsign>.

    Title says it all really, this command lists all the databases defined in the system. It is also aliased to SHOW/COMMAND. +dbcreate <name> (9) + +

    + +dbcreate <name> Create a database entry + + +

    +dbcreate <name> chain <name> [<name>..] (9) + +

    + +dbcreate <name> chain <name> [<name>..] Create a chained database entry + + +

    +dbcreate <name> cmd <dxspider command> (9) + +

    + +dbcreate <name> cmd <dxspider command> make a local command available as a DB + + +

    +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 staement 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:- + + + 's' => [ + .. + .. + '^sh\w*/buc', 'dbshow buckmaster', 'dbshow', + .. + .. + ], + + +to allow + + + SH/BUCK g1tlh + + +to work as they may be used to. + +You can also make local commands available as 'pseudo' databases. You +can therefore make spider special commands available as a database. I +imagine that this will be primarily useful for remote access from +legacy nodes. For example:- + + + DBCREATE dxqsl cmd show/dxqsl + + +You also use one of these databases in a chain. This may be useful +locally. + +See DBIMPORT for the importing of existing AK1A format data to databases. +See DBSHOW for generic database enquiry + +dbcreate <name> remote <node> (9) + +

    + +dbcreate <name> remote <node> Create a remote database entry + + +

    +dbimport <dbname> <filename> (9) + +

    + +dbimport <dbname> <filename> Import AK1A data into a database + + +

    +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 <dbname> (9) + +

    + +dbremove <dbname> Delete a database + + +

    +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. dbshow <dbname> <key> (0)

    @@ -2399,6 +2557,73 @@ SHOW/COMMAND to find out) you can do the same thing with: DBSHOW buck G1TLH +debug (9) + +

    + +debug Set the cluster program into debug mode + + +

    +Executing this command will only have an effect if you are running the cluster +in debug mode i.e. + + + perl -d cluster.pl + + +It will interrupt the cluster just after the debug command has finished. +delete/usdb <callsign> ... (9) + +

    + +delete/usdb <callsign> ... Delete this user from the US State Database + + +

    +This command will completely remove a one or more callsigns +from the US States database. + +There is NO SECOND CHANCE. + +It goes without saying that you should use this command CAREFULLY! + +Note that these callsign may be re-instated by any weekly updates from +the FCC. +delete/user <callsign> ... (9) + +

    + +delete/user <callsign> ... Delete this user from the User Database + + +

    +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! +demonstrate <call> <command> (9) + +

    + +demonstrate <call> <command> Demonstrate a command to another user + + +

    +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. + + + DEMO g7brn sh/dx iota oc209 + DEMO g1tlh set/here + + +Note that this command is similar to SPOOF and will have the same side +effects. Commands are run at the privilege of the user which is being +demonstrated to. directory (0)

    @@ -2597,6 +2822,45 @@ produces:- on the output. +export <msgno> <filename> (9) + +

    + +export <msgno> <filename> Export a message to a file + + +

    +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_users [<filename>] (9) + +

    + +export_users [<filename>] Export the users database to ascii + + +

    +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. filtering... (0)

    @@ -2981,6 +3245,77 @@ Remove this message from the entire cluster system as well as your node.

    This is a quick listing that shows which links are connected and some information about them. See WHO for a list of all connections. +load/aliases (9) + +

    + +load/aliases Reload the command alias table + + +

    +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. +load/badmsg (9) + +

    + +load/badmsg Reload the bad msg table + + +

    +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. +load/badwords (9) + +

    + +load/badwords Reload the bad words table + + +

    +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. +load/bands (9) + +

    + +load/bands Reload the band limits table + + +

    +Reload the /spider/data/bands.pl file if you have changed it manually whilst +the cluster is running. +load/cmd_cache (9) + +

    + +load/cmd_cache Reload the automatic command cache + + +

    +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. +load/forward (9) + +

    + +load/forward Reload the msg forwarding routing table + + +

    +Reload the /spider/msg/forward.pl file if you have changed it +manually whilst the cluster is running. load/keps (5)

    @@ -3010,6 +3345,30 @@ If there is a message number, then it will take the message, run convkeps.pl on it and then load the data, all in one step. These messages are sent to ALL by GB7DJK (and others) from time to time. +load/messages (9) + +

    + +load/messages Reload the system messages file + + +

    +If you change the /spider/perl/Messages file (usually whilst +fiddling/writing new 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' +load/prefixes (9) + +

    + +load/prefixes Reload the prefix table + + +

    +Reload the /spider/data/prefix_data.pl file if you have changed it +manually whilst the cluster is running. merge <node> [<no spots>/<no wwv>] (5)

    @@ -3025,6 +3384,43 @@ 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). +msg <cmd> <msgno> [data ... ] (9) + +

    + +msg <cmd> <msgno> [data ... ] Alter various message parameters + + +

    +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. + + + MSG TO <msgno> <call> - change TO callsign to <call> + MSG FRom <msgno> <call> - change FROM callsign to <call> + MSG PRrivate <msgno> - set private flag + MSG NOPRrivate <msgno> - unset private flag + MSG RR <msgno> - set RR flag + MSG NORR <msgno> - unset RR flag + MSG KEep <msgno> - set the keep flag (message won't be deleted ever) + MSG NOKEep <msgno> - unset the keep flag + MSG SUbject <msgno> <new> - change the subject to <new> + MSG WAittime <msgno> - remove any waitting time for this message + MSG NOREad <msgno> - mark message as unread + MSG REad <msgno> - mark message as read + MSG QUeue - queue any outstanding bulletins + MSG QUeue 1 - queue any outstanding private messages + + +You can look at the status of a message by using:- + + + STAT/MSG <msgno> + + +This will display more information on the message than DIR does. + pc <call> <text> (8)

    @@ -3444,6 +3840,65 @@ You can reply to a message and the subject will automatically have 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) +save [-d -t -a] <filename> "<cmd>" [...] (9) + +

    + +save [-d -t -a] <filename> "<cmd>" [...] Save command output to a file + + +

    +This sysop only cammand allows you to save the output of one or more +commands to a file. For example:- + + + save /spider/packclus/dxstats show/dxstat + + +will save the output of the normal command "show/dxstat" to the file +"dxstats" in the files area. + +You can have some extra flags to the save which will either +date stamp or time stamp or both the filename so:- + + + save -d /tmp/a <cmd> creates /tmp/a_6-Jan-2002 + save -t /tmp/a <cmd> creates /tmp/a_2301Z + save -d -t /tmp/a <cmd> creates /tmp/a_6-Jan-2002_2301Z + + +The -a flag means append to the file instead of overwriting it. + +You can have more than one command on the line, to do this you MUST +enclose each command in double quotes (") eg:- + + + save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats" + + +or + + + save /tmp/a "sh/hfstats","blank +","sh/vhfstats" + + +You can only write into places that the cluster has permission for (which +is that of the "sysop" user [which had BETTER NOT BE "root"]), you will +need to create any directories you want to put stuff in beforehand as well. + +It is likely that you will want to run these commands in a crontab type +situation. You would do that something like:- + + + 0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"') + + +Note that you still enclose each command with (") characters but you must +enclose the entire save command in (') characters. + +Now in fact, this can be varied if you know what you are doing. See the +admin manual for more details. + send <call> [<call> ...] (0)

    @@ -3647,6 +4102,14 @@ You can carry on with the message until you are ready to send it. set/clx <call> [<call>..] Make the callsign an CLX node +

    +set/debug <name> (9) + +

    + +set/debug <name> Add a debug level to the debug set + +

    set/dx (0) @@ -3735,6 +4198,20 @@ eg:-

    +set/isolate (9) + +

    + +set/isolate Isolate a node from the rest of the network + + +

    +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. + set/language <lang> (0)

    @@ -3753,6 +4230,14 @@ and nl (Dutch). set/location <lat & long> Set your latitude and longitude +

    +set/lockout <call> (9) + +

    + +set/lockout <call> Stop a callsign connecting to the cluster + +

    set/logininfo (0) @@ -3843,6 +4328,90 @@ 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. +set/password <callsign> <string> (9) + +

    + +set/password <callsign> <string> Set a users password + + +

    +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. +set/pinginterval <time> <nodecall> (9) + +

    + +set/pinginterval <time> <nodecall> Set ping time to neighbouring nodes + + +

    +As from release 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 30 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. + +If you must change it (and it may be useful for internet connected nodes +on dynamic IP addresses that go away after a set time of usage) the time +can be specified as:- + + + 5 which if less than 30 is converted to minutes otherwise is + taken as the no of seconds between pings. + 120s 120 seconds + 5m 5 minutes + 1h 1 hour + + +Please be aware that this causes traffic to occur on the link, setting +this value too low may annoy your neighbours beyond the point of +endurance! + +You can switch this off by setting it to 0. +set/privilege <n> <call> [<call..] (9) + +

    + +set/privilege <n> <call> [<call..] Set privilege level on a call + + +

    +Set the privilege level on a callsign. The privilege levels that pertain +to commands are as default:- + + 0 - normal user + 1 - allow remote nodes normal user RCMDs + 5 - various privileged commands (including shutdown, but not disc- + connect), the normal level for another node. + 8 - more privileged commands (including disconnect) + 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS + LEVEL. + +If you are a sysop and you come in as a normal user on a remote connection +your privilege will automatically be set to 0. set/prompt <string> (0)

    @@ -3879,6 +4448,14 @@ Tell the system where you are. For example:- SET/QTH East Dereham, Norfolk +set/register <call> ... (9) + +

    + +set/register <call> ... Mark a user as registered + + +

    set/spider <call> [<call>..] (5)

    @@ -3889,6 +4466,29 @@ Tell the system where you are. For example:-

    Tell the system that the call(s) are to be treated as DXSpider node and fed new style DX Protocol rather normal user commands. +set/sys_location <lat & long> (9) + +

    + +set/sys_location <lat & long> Set your cluster latitude and longitude + + +

    +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:- + + SET/LOCATION 52 22 N 0 57 E + + +set/sys_qra <locator> (9) + +

    + +set/sys_qra <locator> Set your cluster QRA Grid locator + + +

    set/talk (0)

    @@ -3897,6 +4497,23 @@ fed new style DX Protocol rather normal user commands.

    +set/usdb <call> <state> <city> (9) + +

    + +set/usdb <call> <state> <city> add/update a US DB callsign + + +

    +This command allows you to add or alter a callsign in the US state +database. Use with extreme caution. Anything you do here will be +overwritten by any weekly updates that affect this callsign + + + set/usdb g1tlh nh downtown rindge + + +see also DELETE/USDB set/usstate (0)

    @@ -4069,6 +4686,14 @@ and returns any information available for that callsign. This service is provided for users of this software by http://www.qslinfo.de. See also SHOW/QRZ, SHOW/WM7D. +show/debug (9) + +

    + +show/debug Show what levels of debug information you are logging + + +

    show/dx (0)

    @@ -4343,6 +4968,14 @@ all the categories will be listed. show/isolate Show list of ISOLATED nodes +

    +show/lockout <prefix>|all (9) + +

    + +show/lockout <prefix>|all Show the list of locked out or excluded callsigns + +

    show/log [<callsign>] (8) @@ -4593,6 +5226,14 @@ and returns any information available for that callsign. This service is provided for users of this software by http://www.qrz.com See also SHOW/WM7D for an alternative. +show/registered [<prefix>] (9) + +

    + +show/registered [<prefix>] Show the registered users + + +

    show/route <callsign> ... (0)

    @@ -4850,6 +5491,25 @@ Display the most recent WWV information that has been received by the system

    Shutdown the cluster and disconnect all the users +spoof <call> <command> (9) + +

    + +spoof <call> <command> Do a command as though you are another user + + +

    +This command is provided so that sysops can set a user's parameters without +me having to write a special 'sysop' version for every user command. It +allows you to pretend that you are doing the command as the user you specify. + +eg:- + + + SPOOF G1TLH set/name Dirk + SPOOF G1TLH set/qra JO02LQ + + stat/channel [<callsign>] (5)

    @@ -5231,6 +5891,25 @@ will allow text with this word again.

    +unset/debug <name> (9) + +

    + +unset/debug <name> Remove a debug level from the debug set + + +

    +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 SHOW/DEBUG unset/dx (0)

    @@ -5366,6 +6045,23 @@ You can unset the hops with command UNSET/HOPS. For example:- unset/hops gb7mbc spots +unset/isolate (9) + +

    + +unset/isolate Stop Isolation of a node from the rest of the network + + +

    +Remove isolation from a node - SET/ISOLATE +unset/lockout <call> (9) + +

    + +unset/lockout <call> Allow a callsign to connect to the cluster + + +

    unset/logininfo (0)

    @@ -5374,6 +6070,16 @@ You can unset the hops with command UNSET/HOPS. For example:-

    +unset/password <call> ... (9) + +

    + +unset/password <call> ... Delete (remove) a user's password + + +

    +This command allows the sysop to completely delete and remove a +password for a user. unset/privilege (0)

    @@ -5405,6 +6111,31 @@ fixed prompt). UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back to normal. +unset/register <call> ... (9) + +

    + +unset/register <call> ... Mark a user as not registered + + +

    +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. + unset/talk (0)

    diff --git a/sgml/installation_en.sgml b/sgml/installation_en.sgml index c0fc5edb..de183687 100644 --- a/sgml/installation_en.sgml +++ b/sgml/installation_en.sgml @@ -8,7 +8,7 @@ Iain Philipps, G0RDI (g0rdi@77hz.com), Ian Maude, G0VGS, (g0vgs@gb7mbc.net) and Charlie Carroll, K1XX, (k1xx@ptcnh.net) -February 2003 revision 0.6 +March 2003 revision 0.7 A reference for SysOps of the DXSpider DXCluster program. @@ -1835,7 +1835,7 @@ then a connect attempt will be started.

    There are probably lots of other things you could use this crontab file for. If you want to know more about it, look at the - website + website at the cron page where it is explained more fully. diff --git a/txt/adminmanual_en.txt b/txt/adminmanual_en.txt index 71e3fc31..64631528 100644 --- a/txt/adminmanual_en.txt +++ b/txt/adminmanual_en.txt @@ -98,192 +98,233 @@ 11.27 clear/wwv [1|all] (0) 11.28 connect (5) 11.29 dbavail (0) - 11.30 dbshow (0) - 11.31 directory (0) - 11.32 directory - (0) - 11.33 directory (0) - 11.34 directory all (0) - 11.35 directory from (0) - 11.36 directory new (0) - 11.37 directory own (0) - 11.38 directory subject (0) - 11.39 directory to (0) - 11.40 directory- (5) - 11.41 disconnect [ ...] (8) - 11.42 dx [by ] (0) - 11.43 echo (0) - 11.44 filtering... (0) - 11.45 forward/latlong (8) - 11.46 forward/opernam (1) - 11.47 help (0) - 11.48 init (5) - 11.49 kill (5) - 11.50 kill - (0) - 11.51 kill - (5) - 11.52 kill [ [ ...] (0) - 11.54 kill expunge [ (5) - 11.56 kill full [ [ (5) - 11.59 kill from (0) - 11.60 kill to (0) - 11.61 links (0) - 11.62 load/keps (5) - 11.63 load/keps [nn] (5) - 11.64 merge [/] (5) - 11.65 pc (8) - 11.66 ping (1) - 11.67 rcmd (1) - 11.68 read (0) - 11.69 read (0) - 11.70 read- (5) - 11.71 reject (0) - 11.72 reject/announce [input] [0-9] (8) - 11.73 reject/announce [0-9] (0) - 11.74 reject/route [0-9] (8) - 11.75 reject/spots [input] [0-9] (8) - 11.76 reject/spots [0-9] (0) - 11.77 reject/wcy [input] [0-9] (8) - 11.78 reject/wcy [0-9] (0) - 11.79 reject/wwv [input] [0-9] (8) - 11.80 reject/wwv [0-9] (0) - 11.81 reply (0) - 11.82 reply (0) - 11.83 reply b (0) - 11.84 reply noprivate (0) - 11.85 reply rr (0) - 11.86 send [ ...] (0) - 11.87 send copy (0) - 11.88 send noprivate (0) - 11.89 send private (0) - 11.90 send rr (0) - 11.91 set/address (0) - 11.92 set/announce (0) - 11.93 set/anntalk (0) - 11.94 set/arcluster [..] (5) - 11.95 set/baddx .. (8) - 11.96 set/badnode .. (8) - 11.97 set/badspotter .. (8) - 11.98 set/badword .. (8) - 11.99 set/bbs [..] (5) - 11.100 set/beep (0) - 11.101 set/clx [..] (5) - 11.102 set/dx (0) - 11.103 set/dxcq (0) - 11.104 set/dxgrid (0) - 11.105 set/dxitu (0) - 11.106 set/dxnet [..] (5) - 11.107 set/echo (0) - 11.108 set/email ... (0) - 11.109 set/here (0) - 11.110 set/homenode (0) - 11.111 set/hops ann|spots|route|wwv|wcy (8) - 11.112 set/language (0) - 11.113 set/location (0) - 11.114 set/logininfo (0) - 11.115 set/name (0) - 11.116 set/node [..] (5) - 11.117 set/obscount (8) - 11.118 set/page (0) - 11.119 set/password (0) - 11.120 set/prompt (0) - 11.121 set/qra (0) - 11.122 set/qth (0) - 11.123 set/spider [..] (5) - 11.124 set/talk (0) - 11.125 set/usstate (0) - 11.126 set/wcy (0) - 11.127 set/wwv (0) - 11.128 set/wx (0) - 11.129 show/baddx (1) - 11.130 show/badnode (1) - 11.131 show/badspotter (1) - 11.132 show/badword (1) - 11.133 show/configuration [] (0) - 11.134 show/configuration/node (0) - 11.135 show/connect (1) - 11.136 show/contest (0) - 11.137 show/date [|] (0) - 11.138 show/db0sdx (0) - 11.139 show/dx (0) - 11.140 show/dxcc (0) - 11.141 show/dxqsl (0) - 11.142 show/dxstats [days] [date] (0) - 11.143 show/files [ []] (0) - 11.144 show/filter (0) - 11.145 show/hfstats [days] [date] (0) - 11.146 show/hftable [days] [date] [prefix ...] (0) - 11.147 show/hops [ann|spots|route|wcy|wwv] (8) - 11.148 show/isolate (1) - 11.149 show/log [] (8) - 11.150 show/moon [ndays] [|] (0) - 11.151 show/muf [][long] (0) - 11.152 show/newconfiguration [] (0) - 11.153 show/newconfiguration/node (0) - 11.154 show/node [ ...] (1) - 11.155 show/prefix (0) - 11.156 show/program (5) - 11.157 show/qra (0) - 11.158 show/qra [] (0) - 11.159 show/qrz (0) - 11.160 show/route ... (0) - 11.161 show/satellite [ ] (0) - 11.162 show/station all [] (6) - 11.163 show/station [ ..] (0) - 11.164 show/sun [ndays] [|] (0) - 11.165 show/time [|] (0) - 11.166 show/usdb [call ..] (0) - 11.167 show/vhfstats [days] [date] (0) - 11.168 show/vhftable [days] [date] [prefix ...] (0) - 11.169 show/wcy (0) - 11.170 show/wcy (0) - 11.171 show/wm7d (0) - 11.172 show/wwv (0) - 11.173 show/wwv (0) - 11.174 shutdown (5) - 11.175 stat/channel [] (5) - 11.176 stat/db (5) - 11.177 stat/msg (1) - 11.178 stat/msg (1) - 11.179 stat/route_node (5) - 11.180 stat/route_node all (5) - 11.181 stat/route_user (5) - 11.182 stat/route_user all (5) - 11.183 stat/user [] (5) - 11.184 sysop (0) - 11.185 talk > [] (0) - 11.186 talk [] (0) - 11.187 type / (0) - 11.188 uncatchup all|[msgno> ...] (5) - 11.189 unset/announce (0) - 11.190 unset/anntalk (0) - 11.191 unset/baddx .. (8) - 11.192 unset/badnode .. (8) - 11.193 unset/badspotter .. (8) - 11.194 unset/badword .. (8) - 11.195 unset/beep (0) - 11.196 unset/dx (0) - 11.197 unset/dxcq (0) - 11.198 unset/dxgrid (0) - 11.199 unset/dxitu (0) - 11.200 unset/echo (0) - 11.201 unset/email (0) - 11.202 unset/here (0) - 11.203 unset/hops ann|spots|route|wwv|wcy (8) - 11.204 unset/logininfo (0) - 11.205 unset/privilege (0) - 11.206 unset/prompt (0) - 11.207 unset/talk (0) - 11.208 unset/usstate (0) - 11.209 unset/wcy (0) - 11.210 unset/wwv (0) - 11.211 unset/wx (0) - 11.212 who (0) - 11.213 wx (0) - 11.214 wx full (0) - 11.215 wx sysop (5) + 11.30 dbcreate (9) + 11.31 dbcreate chain [..] (9) + 11.32 dbcreate cmd (9) + 11.33 dbcreate remote (9) + 11.34 dbimport (9) + 11.35 dbremove (9) + 11.36 dbshow (0) + 11.37 debug (9) + 11.38 delete/usdb ... (9) + 11.39 delete/user ... (9) + 11.40 demonstrate (9) + 11.41 directory (0) + 11.42 directory - (0) + 11.43 directory (0) + 11.44 directory all (0) + 11.45 directory from (0) + 11.46 directory new (0) + 11.47 directory own (0) + 11.48 directory subject (0) + 11.49 directory to (0) + 11.50 directory- (5) + 11.51 disconnect [ ...] (8) + 11.52 dx [by ] (0) + 11.53 echo (0) + 11.54 export (9) + 11.55 export_users [] (9) + 11.56 filtering... (0) + 11.57 forward/latlong (8) + 11.58 forward/opernam (1) + 11.59 help (0) + 11.60 init (5) + 11.61 kill (5) + 11.62 kill - (0) + 11.63 kill - (5) + 11.64 kill [ [ ...] (0) + 11.66 kill expunge [ (5) + 11.68 kill full [ [ (5) + 11.71 kill from (0) + 11.72 kill to (0) + 11.73 links (0) + 11.74 load/aliases (9) + 11.75 load/badmsg (9) + 11.76 load/badwords (9) + 11.77 load/bands (9) + 11.78 load/cmd_cache (9) + 11.79 load/forward (9) + 11.80 load/keps (5) + 11.81 load/keps [nn] (5) + 11.82 load/messages (9) + 11.83 load/prefixes (9) + 11.84 merge [/] (5) + 11.85 msg [data ... ] (9) + 11.86 pc (8) + 11.87 ping (1) + 11.88 rcmd (1) + 11.89 read (0) + 11.90 read (0) + 11.91 read- (5) + 11.92 reject (0) + 11.93 reject/announce [input] [0-9] (8) + 11.94 reject/announce [0-9] (0) + 11.95 reject/route [0-9] (8) + 11.96 reject/spots [input] [0-9] (8) + 11.97 reject/spots [0-9] (0) + 11.98 reject/wcy [input] [0-9] (8) + 11.99 reject/wcy [0-9] (0) + 11.100 reject/wwv [input] [0-9] (8) + 11.101 reject/wwv [0-9] (0) + 11.102 reply (0) + 11.103 reply (0) + 11.104 reply b (0) + 11.105 reply noprivate (0) + 11.106 reply rr (0) + 11.107 save [-d -t -a] "" [...] (9) + 11.108 send [ ...] (0) + 11.109 send copy (0) + 11.110 send noprivate (0) + 11.111 send private (0) + 11.112 send rr (0) + 11.113 set/address (0) + 11.114 set/announce (0) + 11.115 set/anntalk (0) + 11.116 set/arcluster [..] (5) + 11.117 set/baddx .. (8) + 11.118 set/badnode .. (8) + 11.119 set/badspotter .. (8) + 11.120 set/badword .. (8) + 11.121 set/bbs [..] (5) + 11.122 set/beep (0) + 11.123 set/clx [..] (5) + 11.124 set/debug (9) + 11.125 set/dx (0) + 11.126 set/dxcq (0) + 11.127 set/dxgrid (0) + 11.128 set/dxitu (0) + 11.129 set/dxnet [..] (5) + 11.130 set/echo (0) + 11.131 set/email ... (0) + 11.132 set/here (0) + 11.133 set/homenode (0) + 11.134 set/hops ann|spots|route|wwv|wcy (8) + 11.135 set/isolate (9) + 11.136 set/language (0) + 11.137 set/location (0) + 11.138 set/lockout (9) + 11.139 set/logininfo (0) + 11.140 set/name (0) + 11.141 set/node [..] (5) + 11.142 set/obscount (8) + 11.143 set/page (0) + 11.144 set/password (0) + 11.145 set/password (9) + 11.146 set/pinginterval