X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=txt%2Fadminmanual.txt;h=d8078515dd125c5efae856265fa768b1e498f5d3;hb=c9b73a6f1b6aa8c0496a6a7afd1542806ac1a577;hp=5887f5fc60f71bfefbccd830798bb06d78febae0;hpb=f522780bffd435c31b544944063da62a86f9c363;p=spider.git diff --git a/txt/adminmanual.txt b/txt/adminmanual.txt index 5887f5fc..d8078515 100644 --- a/txt/adminmanual.txt +++ b/txt/adminmanual.txt @@ -1917,6 +1917,7 @@ + You can create aliases for commands at will. Beware though, these may not always turn out as you think. Care is needed and you need to test the results once you have set an alias. @@ -1950,9 +1951,11 @@ + would export message number 5467 as a file called keps.in in the /spider/perl directory. + Now login to a VT as sysop and cd /spider/perl. There is a command in the perl directory called convkeps.pl. All we need to do now is convert the file like so ... @@ -1964,6 +1967,7 @@ + Now go back to the cluster and issue the command ... @@ -1973,9 +1977,8 @@ - That is it! the kepler data has been updated. - + That is it! the kepler data has been updated. 6.8. The QRZ callbook @@ -2040,6 +2043,7 @@ registered users, use the command show/register. + 7.2. Passwords At the moment, passwords only affect users who login to a DXSpider @@ -2106,10 +2110,10 @@ CVS repository and then update your Spider source. There are several steps which are listed below ... - First login as the user sysop. Next you need to connect to the CVS repository. You do this with the command below ... + cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login @@ -2238,9 +2242,9 @@ dest eg: 6MUK,WDX (distros) + some examples:- - some examples:- acc/ann dest 6MUK acc/ann 2 by_zone 14,15,16 @@ -2304,10 +2308,10 @@ more info. Please read this to understand how filters work - it will save a lot of grief later on. - You can use any of the following things in this line:- + call the callsign of the thingy call_dxcc eg: 61,62 (from eg: sh/pre G) call_itu @@ -2358,19 +2362,33 @@ - freq eg: 0/30000 or hf or hf/cw or 6m,4m,2m - on same as 'freq' - call eg: G,PA,HB9 - info eg: iota or qsl - by - call_dxcc eg: 61,62 (from eg: sh/pre G) - call_itu - call_zone - by_dxcc - by_itu - by_zone - origin - channel + + + + + + + + + + + + + freq eg: 0/30000 or hf or hf/cw or 6m,4m,2m + on same as 'freq' + call eg: G,PA,HB9 + info eg: iota or qsl + by + call_dxcc eg: 61,62 (from eg: sh/pre G) + call_itu + call_zone + by_dxcc + by_itu + by_zone + origin + channel + + @@ -2432,23 +2450,15 @@ - - - - - - - - - by eg: G,M,2 - origin - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - by_dxcc - by_itu - by_zone - channel + by eg: G,M,2 + origin + origin_dxcc eg: 61,62 (from eg: sh/pre G) + origin_itu + origin_zone + by_dxcc + by_itu + by_zone + channel @@ -2490,15 +2500,21 @@ - by eg: G,M,2 - origin - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - by_dxcc - by_itu - by_zone - channel + + + + + + + by eg: G,M,2 + origin + origin_dxcc eg: 61,62 (from eg: sh/pre G) + origin_itu + origin_zone + by_dxcc + by_itu + by_zone + channel @@ -2506,6 +2522,7 @@ for example + accept/wwv by_zone 4 @@ -2555,9 +2572,6 @@ This command will send your announcement across the whole cluster network. - - - 9.12. announce sysop (5) announce sysop @@ -2571,7 +2585,6 @@ apropos Search the help database - Search the help database for (it isn't case sensitive), and print the names of all the commands that may be relevant. @@ -2637,7 +2650,6 @@ This command allows you to clear (remove) a line in a route filter or to remove the whole filter. - see CLEAR/SPOTS for a more detailed explanation. A sysop can clear an input or normal output filter for a user or the @@ -2701,9 +2713,6 @@ node_default or user_default. - - - 9.20. clear/wcy (0) clear/wcy [1|all] Clear a WCY filter line @@ -2826,6 +2835,7 @@ to allow + SH/BUCK g1tlh to work as they may be used to. @@ -2834,8 +2844,6 @@ databases. See DBSHOW for generic database enquiry - - 9.27. dbimport (9) dbimport Import AK1A data into a database @@ -2894,11 +2902,10 @@ but if he hasn't and the database really does exist (use DBAVAIL or SHOW/COMMAND to find out) you can do the same thing with: + DBSHOW buck G1TLH - DBSHOW buck G1TLH - @@ -2959,15 +2966,20 @@ - DIR TO G1TLH 5 - or - DIR SUBJECT IOTA 200-250 + + + DIR TO G1TLH 5 + or + DIR SUBJECT IOTA 200-250 You can abbreviate all the commands to one letter and use ak1a syntax:- + + + DIR/T G1* 10 DIR/S QSL 10-100 5 @@ -3021,7 +3033,8 @@ - DX by G1TLH FR0G 144.600 he isn't on the cluster + + DX by G1TLH FR0G 144.600 he isn't on the cluster @@ -3034,6 +3047,7 @@ export 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 @@ -3165,7 +3179,6 @@ clear/spots 1 - To remove the filter in its entirty:- clear/spots all @@ -3283,6 +3296,8 @@ same subject will be deleted. Beware! + + 9.46. kill/expunge (6) kill/expunge [..]Expunge a message @@ -3298,6 +3313,7 @@ It otherwise is used in the same way as the KILL command. + 9.47. links (0) links Show which nodes are physically connected @@ -3348,7 +3364,6 @@ 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. @@ -3364,6 +3379,8 @@ 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. + + 9.53. load/forward (9) load/forward Reload the msg forwarding routing table @@ -3413,37 +3430,26 @@ msg [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 - change TO callsign to - MSG FRom - change FROM callsign to - MSG PRrivate - set private flag - MSG NOPRrivate - unset private flag - MSG RR - set RR flag - MSG NORR - unset RR flag - MSG KEep - set the keep flag (message won't be deleted ever) - MSG NOKEep - unset the keep flag - MSG SUbject - change the subject to - MSG WAittime - remove any waitting time for this message - MSG NOREad - mark message as unread - MSG REad - mark message as read - MSG QUeue - queue any outstanding bulletins - MSG QUeue 1 - queue any outstanding private messages + MSG TO - change TO callsign to + MSG FRom - change FROM callsign to + MSG PRrivate - set private flag + MSG NOPRrivate - unset private flag + MSG RR - set RR flag + MSG NORR - unset RR flag + MSG KEep - set the keep flag (message won't be deleted ever) + MSG NOKEep - unset the keep flag + MSG SUbject - change the subject to + MSG WAittime - remove any waitting time for this message + MSG NOREad - mark message as unread + MSG REad - mark message as read + MSG QUeue - queue any outstanding bulletins + MSG QUeue 1 - queue any outstanding private messages @@ -3487,6 +3493,9 @@ + + + 9.60. rcmd (1) rcmd Send a command to another DX cluster @@ -3495,7 +3504,6 @@ This command allows you to send nearly any command to another DX Cluster node that is connected to the system. - Whether you get any output is dependant on a) whether the other system knows that the node callsign of this cluster is in fact a node b) whether the other system is allowing RCMDs from this node and c) @@ -3553,6 +3561,7 @@ + some examples:- @@ -3619,16 +3628,11 @@ origin_itu origin_zone - - - - some examples:- - - rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes) + rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes) @@ -3690,10 +3694,6 @@ rej/spot 1 on hf rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16) - - - - You can use the tag 'all' to reject everything eg: