X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=sgml%2Fadminmanual.sgml;h=bd485b4163ca40e7b533208969faf3f332b7e077;hb=b79059a0422dc8594886b86a38925e2e3e978e1d;hp=9f63b394820534d48e1a34df32e96b6e07da6c21;hpb=564548091fc1c40f493d4bcdc104a4ce3b2ded51;p=spider.git diff --git a/sgml/adminmanual.sgml b/sgml/adminmanual.sgml index 9f63b394..bd485b41 100644 --- a/sgml/adminmanual.sgml +++ b/sgml/adminmanual.sgml @@ -6,7 +6,7 @@
-Last modified: 25 July 2000 by Ian Maude, G0VGS
+Last modified: 02 January 2001 by Ian Maude, G0VGS
-This section describes the installation of DX Spider v1.35 on a
-I am assuming a general knowledge of Linux and its commands. You should know how to use tar and how to edit files using your favourite editor.
+I am assuming a general knowledge of Linux and its commands. You should
+know how to use tar and how to edit files using your favourite editor.
-The crucial ingredient for all of this is In addition to the standard Red Hat distribution you will require the following In addition to the standard Red Hat distribution you will require the
+following
-Do get the latest versions of these packages and install them but use the above list as the earliest versions usable.
+Do get the latest versions of these packages and install them
+but use the above list as the earliest versions usable.
-I will assume that you have already downloaded the latest tarball of the DXSpider software and are ready to install it. I am assuming version 1.35 for this section but of course you would use the latest version.
+I will assume that you have already downloaded the latest tarball of
+the DXSpider software and are ready to install it. I am assuming version
+1.35 for this section but of course you would use the latest version.
-Login as root and create a user to run the cluster under.
-Now to unpack the DX Spider distribution, set symbolic links and group permissions. Copy the tarball to /home/sysop and do the following.
+Now to unpack the DX Spider distribution, set symbolic links and group
+permissions. Copy the tarball to /home/sysop and do the following.
-This last step allows various users of the group spider to have write access to all the directories. This is not really needed just yet but will be useful when web interfaces start to appear.
+This last step allows various users of the group spider to have
+write access to all the directories. This is not really needed just yet
+but will be useful when web interfaces start to appear.
-Finally, you need to fix the permissions on the ax25_call and netrom_call programs. Check where they are with the locate command and alter the permissions with the chmod command like this ..
+Finally, you need to fix the permissions on the ax25_call and netrom_call
+programs. Check where they are with the locate command and alter
+the permissions with the chmod command like this ..
-Now login to your machine as the user you created earlier. In my case that user is called sysop. Once logged in, issue the following commands ....
+Now login to your machine as the user you created earlier. In my case that
+user is called sysop. Once logged in, issue the following commands ....
-Using the distributed DXVars.pm as a a template, set your cluster callsign, sysop callsign and other user info to suit your own environment. Note that this a perl file which will be parsed and executed as part of the cluster. If you get it wrong then perl will complain when you start the cluster process. It is important only to alter the text of any section. Some of the lines look a little odd. Take this line for example ....
+Using the distributed DXVars.pm as a a template, set your cluster callsign,
+sysop callsign and other user info to suit your own environment. Note that
+this a perl file which will be parsed and executed as part of the cluster. If
+you get it wrong then perl will complain when you start the cluster process.
+It is important only to alter the text of any section. Some of the lines look
+a little odd. Take this line for example ....
$myemail = "ianmaude\@btinternet.com";
-There appears to be an extra slash in there. However this has to be there for the file to work so leave it in.
+There appears to be an extra slash in there. However this has to be there
+for the file to work so leave it in.
-DON'T alter the DXVars.pm (or any other file) in /spider/perl, they are overwritten with every release. Any files or commands you place in /spider/local or /spider/local_cmd will automagically be used in preference to the ones in /spider/perl EVEN while the cluster is running!
+DON'T alter the DXVars.pm (or any other file) in /spider/perl, they are
+overwritten with every release. Any files or commands you place in /spider/local
+or /spider/local_cmd will automagically be used in preference to the ones in
+/spider/perl EVEN while the cluster is running!
Save the new file and change directory to ../perl ....
@@ -156,7 +196,8 @@ $ cd ../perl
-Now type the following command which creates the basic user file with you as the sysop.
+Now type the following command which creates the basic user file with you as
+the sysop.
-We can now bring spider up for the first time and see if all is well or not! It should look something like this ...
+We can now bring spider up for the first time and see if all is well or not!
+It should look something like this ...
-If all is well then login on another term or console as sysop and cd to /spider/perl. Now issue the following command ...
+If all is well then login on another term or console as sysop and
+cd to /spider/perl. Now issue the following command ...
-This should log you into the cluster as the sysop under the alias callsign we set earlier. In this case the callsign is G0VGS. The cluster callsign is set in the DXVars.pm file in /spider/local. In this case we will assume that this was set as GB7MBC. You should therefore see this when you login ....
+This should log you into the cluster as the sysop under the alias callsign we
+set earlier. In this case the callsign is G0VGS. The cluster callsign is set
+in the DXVars.pm file in /spider/local. In this case we will assume that this
+was set as GB7MBC. You should therefore see this when you login ....
-In earlier versions of Spider, all the processes were Perl scripts. This was fine but with a lot of users your computer memory would soon be used up. To combat this a new client was written in "C". This client only works for incoming connects at the moment. Before you can use it though it has to be "made". CD to /spider/src and type make. You should see the output on your screen and hopefully now have a small C program called client. Leave it in this directory.
+In earlier versions of Spider, all the processes were Perl scripts. This
+was fine but with a lot of users your computer memory would soon be used up.
+To combat this a new client was written in "C". This client only works for
+incoming connects at the moment. Before you can use it though it
+has to be "made". CD to /spider/src and type make. You
+should see the output on your screen and hopefully now have a small C program
+called client. Leave it in this directory.
-As stated previously, the aim of this document is not to tell you how to configure Linux or the ax25 utilities. However, you do need to add a line in your ax25d.conf to allow connections to DXSpider for your users. For each interface that you wish to allow connections on, use the following format ...
+As stated previously, the aim of this document is not to tell you how to
+configure Linux or the ax25 utilities. However, you do need to add a line
+in your ax25d.conf to allow connections to DXSpider for your users. For
+each interface that you wish to allow connections on, use the following format ...
-Allowing telnet connections is quite simple. Firstly you need to add a line in /etc/services to allow connections to a port number, like this ....
+Allowing telnet connections is quite simple. Firstly you need to add a line
+in /etc/services to allow connections to a port number, like this ....
-This needs to be added above the standard services such as ftp, telnet etc. Once this is done, you need to restart inetd like this ....
+This needs to be added above the standard services such as ftp, telnet etc.
+Once this is done, you need to restart inetd like this ....
Now login as sysop and cd spider/perl. You can test that spider is accepting telnet logins by issuing the following command ....
+ Now login as sysop and cd spider/perl. You can test that spider
+is accepting telnet logins by issuing the following command ....
Assuming all is well, then try a telnet from your linux console ....
@@ -263,23 +325,45 @@ You should now get the login prompt and be able to login as before.
-In order to allow cluster node connections, spider needs to know that the connecting callsign is a cluster node. This is the case whether the connect is incoming or outgoing.
-In spider this is a simple task and can be done in runtime.
+In order to allow cluster node connections, spider needs to know that the
+connecting callsign is a cluster node. This is the case whether the connect
+is incoming or outgoing. In spider this is a simple task and can be done in
+runtime.
+
+
+Later versions of Spider can distinguish different software and treat them
+differently. For example, the WCY beacon cannot be handles by AK1A type
+nodes as AK1A does not know what to do with PC73. There are 4 different
+types of node at present and although they may not have any major
+differences at the moment, it allows for compatibility. The 4 types are ...
+
+
+For now, we will assume that the cluster we are going to connect to is an
+AK1A type node.
Start up the cluster as you did before and login as the sysop with client.pl.
-The cluster node I am wanting to make a connection to is GB7BAA but you would obviously use whatever callsign you required.
-At the prompt type ...
+The cluster node I am wanting to make a connection to is GB7BAA but you would
+obviously use whatever callsign you required. At the prompt type ...
-The case does not matter as long as you have a version of DXSpider later than 1.33. Earlier versions required the callsign to be in upper case.
+The case does not matter as long as you have a version of DXSpider later than
+1.33. Earlier versions required the callsign to be in upper case.
-That is now set, it is as simple as that. To prove it, login on yet another console as sysop and issue the command ...
+That is now set, it is as simple as that. To prove it, login on yet another
+console as sysop and issue the command ...
-Because DXSpider operates under Linux, connections can be made using just about any protocol; AX25, NETRom, tcp/ip, ROSE etc are all possible examples. Connect scripts live in the /spider/connect directory and are simple ascii files. Writing a script for connections is therefore relatively simple.
+Because DXSpider operates under Linux, connections can be made using just about
+any protocol; AX25, NETRom, tcp/ip, ROSE etc are all possible examples.
+Connect scripts live in the /spider/connect directory and are simple ascii files.
+Writing a script for connections is therefore relatively simple.
-The connect scripts consist of lines which start with the following keywords or symbols:-
-
+The connect scripts consist of lines which start with the following keywords
+or symbols:-
-Both these examples assume that everything is set up properly at the other end. You will find other examples in the /spider/examples directory.
+Both these examples assume that everything is set up properly at the other end.
+You will find other examples in the /spider/examples directory.
-
-You start the connection, from within a sysop enabled cluster login, by typing in the word connect followed by a script name like this ....
+You start the connection, from within a sysop enabled cluster login, by typing
+in the word connect followed by a script name like this ....
-With later versions of Spider there is a set/login command for users. This tells them when a user or node logs in or out. If you do not add a line to your scripts after the final line (or before the client line which should always be last if needed) then the login/logout information will be sent to users
+Cluster links in particular suffer greatly from the presence of telnet echo.
+This is caused by the telnet negotiation itself and can create at worst severe
+loops. At best it creates unnecessary bandwidth and large logfiles! There are
+things that can be done to limit this problem but will not always work dependent
+on the route taken to connect.
+
+
+Telnet echo itself should only be a problem if the connection is being made to
+the telnet port (23). This port uses special rules that include echo negotiation.
+If the connection is to a different port, such as 8000, this negotiation does
+not happen and therefore no echo should be present.
+
+
+Sometimes it is not possible to make a direct connection to another node and this
+can cause problems. There is a way of trying to suppress the telnet echo but
+this will not always work, unfortunately it is difficult to be more specific.
+Here is an example of what I mean ...
+
+
-Ok, you should now have DXSpider running nicely and allowing connects by cluster nodes or users. However, it has to be shutdown and restarted manually and if connection scripts fail they have to be started again manually too, not much use if you are not at the console!
-So, in this section we will automate both. Firstly starting the cluster.
+Ok, you should now have DXSpider running nicely and allowing connects by cluster
+nodes or users. However, it has to be shutdown and restarted manually and if
+connection scripts fail they have to be started again manually too, not much use
+if you are not at the console! So, in this section we will automate both.
+Firstly starting the cluster.
-
-This is not only a way to start the cluster automatically, it also works as a watchdog, checking the sanity of DXSpider and respawning it should it crash for any reason.
-Before doing the following, shutdown the cluster as you did earlier.
+This is not only a way to start the cluster automatically, it also works as a
+watchdog, checking the sanity of DXSpider and respawning it should it crash for
+any reason. Before doing the following, shutdown the cluster as you did earlier.
-Login as root and bring up the /etc/inittab file in your favourite editor. Add the following lines to the file near the end ...
+Login as root and bring up the /etc/inittab file in your favourite editor. Add
+the following lines to the file near the end ...
-This will automatically start DXSpider on tty7 (ALT-F7) on bootup and restart it should it crash for any reason.
+This will automatically start DXSpider on tty7 (ALT-F7) on bootup and restart
+it should it crash for any reason.
-As root type the command telinit q. DXSpider should start up immediately. You will see the output on tty7 and if you login as sysop you should find everything running nicely.
+As root type the command telinit q. DXSpider should start up
+immediately. You will see the output on tty7 and if you login as sysop
+you should find everything running nicely.
So far so good, now to automate script connections...
-
-Login as sysop and create a file in /spider/local_cmd called crontab. Edit it with your favourite editor and add a line like this (I have included a comment)
+Login as sysop and create a file in /spider/local_cmd called crontab.
+Edit it with your favourite editor and add a line like this (I have included
+a comment)
-The callsign involved will be the callsign of the cluster node you are going to connect to. This will now check every 10 minutes to see if gb7xxx is connected, if it is then nothing will be done. If it is not, then a connect attempt will be started.
+The callsign involved will be the callsign of the cluster node you are
+going to connect to. This will now check every 10 minutes to see if
+gb7xxx is connected, if it is then nothing will be done. If it is not,
+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
-In /spider/data you will find a file called hop_table.pl. This is the file that controls your hop count settings. It has a set of default hops on the various PC frames and also a set for each node you want to alter the hops for. You may be happy with the default settings of course, but this powerful tool can help to protect and improve the network. The file will look something like this ...
+In /spider/data you will find a file called hop_table.pl. This is the file
+that controls your hop count settings. It has a set of default hops on the
+various PC frames and also a set for each node you want to alter the hops for.
+You may be happy with the default settings of course, but this powerful tool
+can help to protect and improve the network. The file will look something
+like this ...
-Each set of hops is contained within a pair of curly braces and contains a series of PC frame types. PC11 for example is a DX spot. The figures here are not exhaustive but should give you a good idea of how the file works.
+Each set of hops is contained within a pair of curly braces and contains a
+series of PC frame types. PC11 for example is a DX spot. The figures here
+are not exhaustive but should give you a good idea of how the file works.
-You can alter this file at any time, including whilst the cluster is running. If you alter the file during runtime, the command load/hops will bring your changes into effect.
+You can alter this file at any time, including whilst the cluster is running.
+If you alter the file during runtime, the command load/hops will
+bring your changes into effect.
-If you use isolate on a node connection you will continue to receive all information from the isolated partner, however you will not pass any information back to the isolated node. There are times when you would like to forward only spots across a link (maybe during a contest for example). To do this, isolate the node in the normal way and put in a filter in the /spider/filter/spots directory to override the isolate. This filter can be very simple and consists of just one line ....
+If you use isolate on a node connection you will continue to receive all
+information from the isolated partner, however you will not pass any information
+back to the isolated node. There are times when you would like to forward only
+spots across a link (maybe during a contest for example). To do this, isolate
+the node in the normal way and put in a filter in the /spider/filter/spots
+directory to override the isolate. This filter can be very simple and consists
+of just one line ....
There is a lot more on filtering in the next section.
-
-Filters can be set for spots, announcements and WWV. You will find the directories for these under /spider/filter. You will find some examples in the directories with the suffix .issue. There are two types of filter, one for incoming information and one for outgoing information. Outgoing filters are in the form CALLSIGN.pl and incoming filters are in the form in_CALLSIGN.pl. Filters can be set for both nodes and users.
+Filters can be set for spots, announcements and WWV. You will find the
+directories for these under /spider/filter. You will find some examples in
+the directories with the suffix .issue. There are two types of
+filter, one for incoming information and one for outgoing information.
+Outgoing filters are in the form CALLSIGN.pl and incoming filters
+are in the form in_CALLSIGN.pl. Filters can be set for both nodes
+and users.
-All filters work in basically the same way. There are several elements delimited by commas.
-There can be many lines in the filter and they are read from the top by the program.
-When writing a filter you need to think carefully about just what you want to achieve. You
-are either going to write a filter to accept or to reject.
-Think of a filter as having 2 main elements. For a reject filter, you would have a line
-or multiple lines rejecting the things you do not wish to receive and then a default
-line accepting everything else that is not included in the filter. Likewise, for an
-accept filter, you would have a line or multiple lines accepting the things you wish
-to receive and a default line rejecting everthing else.
+All filters work in basically the same way. There are several elements
+delimited by commas. There can be many lines in the filter and they are
+read from the top by the program. When writing a filter you need to think
+carefully about just what you want to achieve. You are either going to write
+a filter to accept or to reject. Think of a filter as
+having 2 main elements. For a reject filter, you would have a line or multiple
+lines rejecting the things you do not wish to receive and then a default line
+accepting everything else that is not included in the filter. Likewise, for an
+accept filter, you would have a line or multiple lines accepting the things you
+wish to receive and a default line rejecting everthing else.
In the example below, a user requires a filter that would only return SSB spots
-posted in Europe on the HF bands. This is achieved by first rejecting the CW section
-of each HF band and rejecting all of VHF, UHF etc based on frequency.
+posted in Europe on the HF bands. This is achieved by first rejecting the CW
+section of each HF band and rejecting all of VHF, UHF etc based on frequency.
Secondly, a filter rule is set based on CQ zones to only accept spots posted in
Europe. Lastly, a default filter rule is set to reject anything outside the filter.
@@ -632,7 +814,8 @@ $in = [
-The actual elements of each filter are described more fully in the following sections.
+The actual elements of each filter are described more fully in the following
+sections.
-There are 3 elements here to look at. Firstly, the action element. This is very simple and only 2 possible states exist, accept (1) or drop (0).
+There are 3 elements here to look at. Firstly, the action element. This is
+very simple and only 2 possible states exist, accept (1) or drop (0).
-The second element is the field_no. There are 13 possiblities to choose from here ....
+The second element is the field_no. There are 13 possiblities to choose from
+here ....
-The third element tells us what to expect in the fourth element. There are 4 possibilities ....
+The third element tells us what to expect in the fourth element. There are
+4 possibilities ....
-The fifth element is simply the hops to set in this filter. This would only be used if the filter was for a node of course and overrides the hop count in hop_table.pl.
+The fifth element is simply the hops to set in this filter. This would only
+be used if the filter was for a node of course and overrides the hop count in
+hop_table.pl.
-So, let's look at an example spot filter. It does not matter in the example who the filter is to be used for.
-So, what do we need in the filter? We need to filter the spots the user/node requires and also set a default rule for anything else outside the filter. Below is a simple filter that stops spots arriving from outside Europe.
+So, let's look at an example spot filter. It does not matter in the example
+who the filter is to be used for. So, what do we need in the filter? We need
+to filter the spots the user/node requires and also set a default rule for
+anything else outside the filter. Below is a simple filter that stops spots
+arriving from outside Europe.
-So the filter is wrapped in between a pair of square brackets. This tells Spider to look in between these limits. Then each line is contained within its own square brackets and ends with a comma.
-Lets look carefully at the first line. The first element is 0 (drop). Therefore anything we put on this line will not be accepted. The next element is 4. This means we are filtering by the spotter. The third element is the letter "a" which tells the program to expect an alphanumeric expression in the fourth element. The fourth element is a list of letters separated by the pipe symbol.
+So the filter is wrapped in between a pair of square brackets. This tells
+Spider to look in between these limits. Then each line is contained within
+its own square brackets and ends with a comma. Lets look carefully at the first
+line. The first element is 0 (drop). Therefore anything we put on this line
+will not be accepted. The next element is 4. This means we are filtering by
+the spotter. The third element is the letter "a" which tells the program to
+expect an alphanumeric expression in the fourth element. The fourth element
+is a list of letters separated by the pipe symbol.
-What this line does is tell the program to drop any spots posted by anyone in the USA, Canada or Japan.
+What this line does is tell the program to drop any spots posted by anyone in
+the USA, Canada or Japan.
-The second line is the default rule for anything else. The "d" tells us this and the line simply reads... accept anything else.
+The second line is the default rule for anything else. The "d" tells us this
+and the line simply reads... accept anything else.
-You can add as many lines as you need to complete the filter but if there are several lines of the same type it is neater to enclose them all as one line. An example of this is where specific bands are set. We could write this like this ....
+You can add as many lines as you need to complete the filter but if there are
+several lines of the same type it is neater to enclose them all as one line.
+An example of this is where specific bands are set. We could write this like
+this ....
-It should be noted that the filter will start to be used only once a user/node has logged out and back in again.
+It should be noted that the filter will start to be used only once a user/node
+has logged out and back in again.
+
+I am not going to spend any more time on these filters now as they will become
+more "comprehensive" in the near future.
+
+
+Upto v1.44 it was not possible for the user to set their own filters. From
+v1.45 though that has all changed. It is now possible to set filters for just
+about anything you wish. If you have just updated from an older version of
+DXSpider you will need to update your new filters. You do not need to do
+anything with your old filters, they will be renamed as you update.
+
+
+There are 3 basic commands involved in setting and manipulating filters. These
+are accept, reject and clear. First we will look
+generally at filtering. There are a number of things you can filter in the
+DXSpider system. They all use the same general mechanism.
+
+
+In general terms you can create a 'reject' or an 'accept' filter which can have
+up to 10 lines in it. You do this using, for example ...
+
+
+and you can check that your filters have worked by the command ...
+
+
+For now we are going to use spots for the examples, but you can apply the same
+principles to all types of filter.
+
+
+There are two main types of filter, accept or reject. You
+can use either to achieve the result you want dependent on your own preference
+and which is more simple to do. It is pointless writing 8 lines of reject
+filters when 1 accept filter would do the same thing! Each filter has 10
+lines (of any length) which are tried in order. If a line matches then the
+action you have specified is taken (ie reject means ignore it and accept
+means take it)
+
+
+If you specify reject filters, then any lines that arrive that match the filter
+will be dumped but all else will be accepted. If you use an accept filter,
+then ONLY the lines in the filter will be accepted and all else will be dumped.
+For example if you have a single line accept filter ...
+
+
+If you set a reject filter like this ...
+
+
+You can arrange your filter lines into logical units, either for your own
+understanding or simply convenience. Here is an example ...
+
+
+This is an example where you would use a line number (1 and 2 in this case), if
+you leave the digit out, the system assumes '1'. Digits '0'-'9' are available.
+This make it easier to see just what filters you have set. It also makes it
+more simple to remove individual filters, during a contest for example.
+
+
+You will notice in the above example that the second line has brackets. Look
+at the line logically. You can see there are 2 separate sections to it. We
+are saying reject spots that are VHF or above APART from those in
+zones 14, 15 and 16 (either spotted there or originated there). If you did
+not have the brackets to separate the 2 sections, then Spider would read it
+logically from the front and see a different expression entirely ...
+
+
+You can filter in several different ways. The options are listed in the
+various helpfiles for accept, reject and filter.
+
+
+Sometimes all that is needed is a general rule for node connects. This can
+be done with a node_default filter. This rule will always be followed, even
+if the link is isolated, unless another filter is set specifically. Default
+rules can be set for nodes and users. They can be set for spots, announces,
+WWV and WCY. They can also be used for hops. An example might look like
+this ...
+
+
+Once you are happy with the results you get, you may like to experiment.
+
+
+The previous example that filters hf/cw spots and accepts vhf/uhf spots from EU
+can be written with a mixed filter, for example ...
+
+
-I am not going to spend any more time on these filters now as they will become more "comprehensive" in the near future.
+It was mentioned earlier that after a reject test that doesn't match, the default
+for following tests is 'accept', the reverse is true for 'accept'. In the example
+what happens is that the reject is executed first, any non hf/cw spot is passed
+to the accept line, which lets through everything else on HF. The next filter line
+lets through just VHF/UHF spots from EU.
+
+
+
-In the /spider/msg directory you will find a file called badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The original looks something like this ....
+In the /spider/msg directory you will find a file called badmsg.pl.issue. Rename
+this to badmsg.pl and edit the file. The original looks something like this ....
-I think this is fairly self explanatory. It is simply a list of subject headers that we do not want to pass on to either the users of the cluster or the other cluster nodes that we are linked to. This is usually because of rules and regulations pertaining to items for sale etc in a particular country.
+I think this is fairly self explanatory. It is simply a list of subject
+headers that we do not want to pass on to either the users of the cluster or
+the other cluster nodes that we are linked to. This is usually because of
+rules and regulations pertaining to items for sale etc in a particular country.
-In the same way as mail, there are some types of spot we do not wish to pass on to users or linked cluster nodes. In the /spider/data directory you will find a file called baddx.pl.issue. Rename this to baddx.pl and edit the file. The original looks like this ....
+In the same way as mail, there are some types of spot we do not wish to pass on
+to users or linked cluster nodes. In the /spider/data directory you will find
+a file called baddx.pl.issue. Rename this to baddx.pl and edit the file. The
+original looks like this ....
-Again, this is simply a list of names we do not want to see in the spotted field of a DX callout.
+Again, this is simply a list of names we do not want to see in the spotted
+field of a DX callout.
+
+
+
+Create a file in /spider/data called badwords. The format is quite
+simple. Lines beginning with # are ignored so comments can be added. An
+example file is below ...
+
+
+You can reload the file from the cluster prompt as sysop with load/badwords.
-One of the more important things a cluster sysop needs to do is to get information to his users. The simplest way to do this is to have a banner that is sent to the user on login. This is know as a "message of the day" or "motd". To set this up, simply create a file in /spider/data called motd and edit it to say whatever you want. It is purely a text file and will be sent automatically to anyone logging in to the cluster.
+One of the more important things a cluster sysop needs to do is to get
+information to his users. The simplest way to do this is to have a banner
+that is sent to the user on login. This is know as a "message of the day"
+or "motd". To set this up, simply create a file in /spider/data called motd
+and edit it to say whatever you want. It is purely a text file and will be
+sent automatically to anyone logging in to the cluster.
-If for any reason the cluster is down, maybe for upgrade or maintenance but the machine is still running, a message can be sent to the user advising them of the fact. This message lives in the /spider/data directory and is called "offline". Simply create the file and edit it to say whatever you wish. This file will be sent to a user attempting to log into the cluster when DXSpider is not actually running.
+If for any reason the cluster is down, maybe for upgrade or maintenance but
+the machine is still running, a message can be sent to the user advising them
+of the fact. This message lives in the /spider/data directory and is called
+"offline". Simply create the file and edit it to say whatever you wish.
+This file will be sent to a user attempting to log into the cluster when
+DXSpider is not actually running.
-You can set other text messages to be read by the user if they input the file name. This could be for news items or maybe information for new users. To set this up, make a directory under /spider called packclus. Under this directory you can create files called news or newuser for example. In fact you can create files with any names you like. These can be listed by the user with the command ....
+You can set other text messages to be read by the user if they input the file
+name. This could be for news items or maybe information for new users.
+To set this up, make a directory under /spider called packclus.
+Under this directory you can create files called news or newuser
+for example. In fact you can create files with any names you like. These can
+be listed by the user with the command ....
-You can also store other information in this directory, either directly or nested under directories. One use for this would be to store DX bulletins such as the OPDX bulletins. These can be listed and read by the user. To keep things tidy, make a directory under /spider/packclus called bulletins. Now copy any OPDX or similar bulletins into it. These can be listed by the user in the same way as above using the show/files command with an extension for the bulletins directory you have just created, like this ....
+You can also store other information in this directory, either directly or
+nested under directories. One use for this would be to store DX bulletins
+such as the OPDX bulletins. These can be listed and read by the user.
+To keep things tidy, make a directory under /spider/packclus called
+bulletins. Now copy any OPDX or similar bulletins into it. These
+can be listed by the user in the same way as above using the show/files
+command with an extension for the bulletins directory you have just created,
+like this ....
-You will find a file in /spider/cmd/ called Aliases. First, copy this file to /spider/local_cmd/Aliases and edit this file. You will see something like this ...
+You will find a file in /spider/cmd/ called Aliases. First, copy this file to
+/spider/local_cmd/Aliases and edit this file. You will see something like this ...
-In later versions of Spider a simple console program is provided for the sysop. This has a type ahead buffer with line editing facilities and colour for spots, announces etc.
-To use this program, simply use console.pl instead of client.pl.
+In later versions of Spider a simple console program is provided for the sysop.
+This has a type ahead buffer with line editing facilities and colour for spots,
+announces etc. To use this program, simply use console.pl instead of client.pl.
-To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the file with your favourite editor.
+To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the
+file with your favourite editor.
-
-Most maintenance tasks are automatic but there are some commands that are useful for a sysop. These are listed below in alphabetical order. The number in brackets following the command name is the permissions level needed to use the command.
-
-
-
-
-Send an announcement to Sysops only
-
-
-
-
-Start a connection process that will culminate in a new connection to the
-DX cluster <callsign>. This process creates a new 'client' process which will
-use the script in /spider/connect/<callsign> to effect the 'chat' exchange
-necessary to traverse the network(s) to logon to the cluster <callsign>.
-
-
-
-
-
-When you send messages the fact that you have forwarded it to another node
-is remembered so that it isn't sent again. When you have a new partner
-node and you add their callsign to your /spider/msg/forward.pl file, all
-outstanding non-private messages will be forwarded to them. This may well
-be ALL the non-private messages. You can prevent this by using these
-commmands:-
-
- catch GB7DJK all
- catch GB7DJK 300 301 302 303
-
-and to undo what you have just done:-
-
- uncatch GB7DJK all
- uncatch GB7DJK 300 301 302 303
+First login as the user sysop. Next you need to connect to the CVS
+repository. You do this with the command below ...
-which will arrange for them to be forward candidates again.
+
-
-
-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'.
+The next step will create a brand new 'spider' directory in your current
+directory.
-You can define a local database with the first form of the command eg:
-
- DBCREATE oblast
+
+Hopefully your screen should show you downloading files. The -z3 simply compresses
+the download to improve speed.
+When this has finished, you will have exactly the same as if you had untarred a full
+tarball PLUS some extra directories and files that CVS needs to do the magic that
+it does.
-No checking is done to see if the any of the chained databases exist, in
-fact it is usually better to do the above statement first then do each of
-the chained databases.
+
+Now if you are doing a new installation, that's it. Carry on as if you have
+just downloaded and untarred the lastest tarball.
-Databases can exist offsite. To define a database that lives on another
-node do:
+
+If you want to upgrade your current installation then do this ...
- DBCREATE buckmaster remote gb7dxc
+
+NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the permissions
+correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T YOU?????
-To see what databases have been defined do:
+Remember to recompile the C client (cd /spider/src; make)
- DBAVAIL (or it will have been aliased to SHOW/COMMAND)
+
+At this point the files have been upgraded. You can (usually) restrt the cluster
+in your own time. However, if you attempt to use any new commands or features
+expect it to be fatal! At least your cluster will have been restarted then so it
+will be too late to worry about it!
-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:-
+
+Now the magic part! From now on when you want to update, simply connect to the
+Internet and then, as the user sysop ...
+You will find any changes documented in the /spider/Changes file.
-to work as they may be used to.
+
+Below is a complete list of commands available from the cluster prompt.
+Most maintenance tasks are automatic but there are some commands that are useful
+for a sysop. These are listed below in alphabetical order. The number in
+brackets following the command name is the permissions level needed to use
+the command.
-
-
-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
+Create an 'accept this announce' line for a filter.
-will import the standard OBLAST database that comes with AK1A into the
-oblast database held locally.
-
-
-
-
-DBREMOVE will completely remove a database entry and also delete any data
-file that is associated with it.
+
-
-Executing this command will only have an effect if you are running the cluster
-in debug mode i.e.
+This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
-
+
+
+Create an 'accept this spot' line for a filter.
+
+
+An accept filter line means that if the spot matches this filter it is
+passed onto the user. See HELP FILTERS for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+
+You can use any of the following things in this line:-
+
+
+For frequencies, you can use any of the band names defined in
+SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
+thus: hf/ssb. You can also just have a simple range like: 0/30000 -
+this is more efficient than saying simply: freq HF (but don't get
+too hung up about that)
+
+some examples:-
+
+
+
+
+This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+
+
+
+
+It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+
+
+There are no examples because WCY Broadcasts only come from one place and
+you either want them or not (see UNSET/WCY if you don't want them).
+
+This command is really provided for future use.
+
+See HELP FILTER for information.
+
+
+
+
+This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+
+
+
+
+It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+
+
+
+
+This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+
+
+
+
+Send an announcement to LOCAL users only, where <text> is the text
+of the announcement you wish to broadcast
+
+
+
+
+This command will send your announcement across the whole cluster
+network.
+
+
+
+
+
+Send an announcement to Sysops only
+
+
+
+
+Search the help database for <string> (it isn't case sensitive),
+and print the names of all the commands that may be relevant.
+
+
+
+
+This will disconnect you from the cluster
+
+
+
+
+When you send messages the fact that you have forwarded it to another node
+is remembered so that it isn't sent again. When you have a new partner
+node and you add their callsign to your /spider/msg/forward.pl file, all
+outstanding non-private messages will be forwarded to them. This may well
+be ALL the non-private messages. You can prevent this by using these
+commmands:-
+
+
+
+
+This command allows you to clear (remove) a line in a spot filter or to
+remove the whole filter.
+
+If you have a filter:-
+
+
+
+
+Start a connection process that will culminate in a new connection to the
+DX cluster <callsign>. This process creates a new 'client' process which will
+use the script in /spider/connect/<callsign> to effect the 'chat' exchange
+necessary to traverse the network(s) to logon to the cluster <callsign>.
+
+
+
+
+The title says it all really, this command lists all the databases defined
+in the system. It is also aliased to SHOW/COMMAND.
+
+
+
+
+DBCREATE allows you to define a database in the system. It doesn't actually
+create anything, just defines it.
+
+The databases that are created are simple DB_File hash databases, they are
+therefore already 'indexed'.
+
+You can define a local database with the first form of the command eg:
+
+ DBCREATE oblast
+
+You can also chain databases with the addition of the 'chain' keyword.
+This will search each database one after the other. A typical example
+is:
+
+ DBCREATE sdx_qsl chain sql_ad
+
+No checking is done to see if the any of the chained databases exist, in
+fact it is usually better to do the above statement first then do each of
+the chained databases.
+
+Databases can exist offsite. To define a database that lives on another
+node do:
+
+ DBCREATE buckmaster remote gb7dxc
+
+Remote databases cannot be chained; however, the last database in a
+a chain can be a remote database eg:
+
+ DBCREATE qsl chain gb7dxc
+
+To see what databases have been defined do:
+
+ DBAVAIL (or it will have been aliased to SHOW/COMMAND)
+
+It would be normal for you to add an entry into your local Aliases file
+to allow people to use the 'SHOW/<dbname>' style syntax. So you would
+need to add a line like:-
+
+
+
+
+If you want to import or update data in bulk to a database you can use
+this command. It will either create or update entries into an existing
+database. For example:-
+
+ DBIMPORT oblast /tmp/OBLAST.FUL
+
+will import the standard OBLAST database that comes with AK1A into the
+oblast database held locally.
+
+
+
+
+DBREMOVE will completely remove a database entry and also delete any data
+file that is associated with it.
+
+There is no warning, no comeback, no safety net.
+
+For example:
+
+ DBREMOVE oblast
+
+will remove the oblast database from the system and it will also remove
+the associated datafile.
+
+I repeat:
+
+There is no warning, no comeback, no safety net.
+
+You have been warned.
+
+
+
+
+This is the generic user interface to the database to the database system.
+It is expected that the sysop will add an entry to the local Aliases file
+so that users can use the more familiar AK1A style of enquiry such as:
+
+
+
+
+Executing this command will only have an effect if you are running the cluster
+in debug mode i.e.
+
+
+
+
+List the messages in the messages directory.
+
+If there is a 'p' one space after the message number then it is a
+personal message. If there is a '-' between the message number and the
+'p' then this indicates that the message has been read.
+
+You can use shell escape characters such as '*' and '?' in the <call>
+fields.
+
+You can combine some of the various directory commands together eg:-
+
+
+Works just like the user command except that sysops can see ALL messages.
+
+
+
+
+Disconnect any <call> connected locally
+
+
+
+
+This is how you send a DX Spot to other users. You can, in fact, now
+enter the <freq> and the <call> either way round.
+
+
+
+
+Export a message to a file. This command can only be executed on a local
+console with a fully privileged user. The file produced will be in a form
+ready to be imported back into the cluster by placing it in the import
+directory (/spider/msg/import).
+
+This command cannot overwrite an existing file. This is to provide some
+measure of security. Any files written will owned by the same user as the
+main cluster, otherwise you can put the new files anywhere the cluster can
+access. For example:-
+
+ EXPORT 2345 /tmp/a
+
+
+
+
+Export the users database to a file in ascii format. If no filename
+is given then it will export the file to /spider/data/user_asc.
+
+If the file already exists it will be renamed to <filename>.o. In fact
+up to 5 generations of the file can be kept each one with an extra 'o' on the
+suffix.
+
+BE WARNED: this will write to any file you have write access to. No check is
+made on the filename (if any) that you specify.
+
+
+
+
+This command sends all the latitude and longitude information that your
+cluster is holding against callsigns. One advantage of recieving this
+information is that more locator information is held by you. This
+means that more locators are given on the DX line assuming you have
+set/dxgrid enabled. This could be a LOT of information though, so
+it is not recommended on slow links.
+
+
+
+
+This command sends out any information held in the user file which can
+be broadcast in PC41 protocol packets. This information is Name, QTH, Location
+and Homenode. PC41s are only sent for the information that is available.
+
+
+
+
+All commands can be abbreviated, so SHOW/DX can be abbreviated
+to SH/DX, ANNOUNCE can be shortened to AN and so on.
+
+Look at the APROPOS <string> command which will search the help database
+for the <string> you specify and give you a list of likely commands
+to look at with HELP.
+
+
+
+
+This command attempts to re-initialise a link to a (usually) AK1A node
+that has got confused, usually by a protocol loop of some kind. It may
+work - but you usually will be better off simply disconnecting it (or
+better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
+node>).
+
+Best of luck - you will need it.
+
+
+
+
+Delete a message from the local system. You will only be able to
+delete messages that you have originated or been sent (unless you are
+the sysop).
+
+
+
+
+You can get rid of any message to or originating from your callsign using
+this command. You can remove more than one message at a time.
+
+As a sysop you can kill any message on the system.
+
+
+Delete a message (usually a 'bulletin') from the whole cluster system.
+
+This uses the subject field, so any messages that have exactly the same subject
+will be deleted. Beware!
+
+
+
+
+This is a quick listing that shows which links are connected and
+some information about them. See WHO for a list of all connections.
+
+
+
+
+
+Reload the /spider/cmd/Aliases file after you have editted it. You will need to
+do this if you change this file whilst the cluster is running in order for the
+changes to take effect.
+
+
+
+Reload the /spider/data/baddx.pl file if you have changed it manually whilst
+the cluster is running. This table contains the DX Calls that, if spotted,
+will not be passed on. FR0G and TEST are classic examples.
+
+
+
+
+Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
+the cluster is running. This table contains a number of perl regular
+expressions which are searched for in the fields targetted of each message.
+If any of them match then that message is immediately deleted on receipt.
+
+
+
+
+Reload the /spider/data/badwords file if you have changed it manually whilst
+the cluster is running. This file contains a list of words which, if found
+on certain text portions of PC protocol, will cause those protocol frames
+to be rejected. It will all put out a message if any of these words are
+used on the announce, dx and talk commands. The words can be one or
+more on a line, lines starting with '#' are ignored.
+
+
+
+
+Reload the /spider/data/bands.pl file if you have changed it manually whilst
+the cluster is running.
+
+
+
+
+Normally, if you change a command file in the cmd or local_cmd tree it will
+automatially be picked up by the cluster program. Sometimes it can get confused
+if you are doing a lot of moving commands about or delete a command in the
+local_cmd tree and want to use the normal one again. Execute this command to
+reset everything back to the state it was just after a cluster restart.
+
+
+
+
+
+
+If you change the /spider/perl/Messages file (usually whilst fiddling/writing ne
+commands) you can have them take effect during a cluster session by executing this
+command. You need to do this if get something like :-
+
+unknown message 'xxxx' in lang 'en'
+
+
+
+
+Reload the /spider/data/prefix_data.pl file if you have changed it manually
+whilst the cluster is running.
+
+
+
+
+MERGE allows you to bring your spot and wwv database up to date. By default
+it will request the last 10 spots and 5 WWVs from the node you select. The
+node must be connected locally.
+
+You can request any number of spots or wwv and although they will be appended
+to your databases they will not duplicate any that have recently been added
+(the last 2 days for spots and last month for WWV data).
+
+
+
+
+Alter message parameters like To, From, Subject, whether private or bulletin
+or return receipt (RR) is required or whether to keep this message from timing
+out.
+
+
+
+
+Send some arbitrary text to a locally connected callsign. No processing is done on
+the text. This command allows you to send PC Protocol to unstick things if problems
+arise (messages get stuck etc). eg:-
+
+ pc gb7djk PC33^GB7TLH^GB7DJK^400^
+
+You can also use in the same way as a talk command to a connected user but
+without any processing, added of "from <blah> to <blah>" or whatever.
+
+ pc G1TLH Try doing that properly!!!
+
+
+
+
+This command is used to estimate the quality of the link to another cluster.
+The time returned is the length of time taken for a PC51 to go to another
+cluster and be returned.
+
+Any visible cluster node can be PINGed.
+
+
+
+
+This command allows you to send nearly any command to another DX Cluster
+node that is connected to the system.
+
+Whether you get any output is dependant on a) whether the other system knows
+that the node callsign of this cluster is in fact a node b) whether the
+other system is allowing RCMDs from this node and c) whether you have
+permission to send this command at all.
+
+
+
+
+You can read any messages that are sent as 'non-personal' and also any
+message either sent by or sent to your callsign.
+
+
+
+
+
+As a sysop you may read any message on the system
+
+
+
+
+Create an 'reject this announce' line for a filter.
+
+An reject filter line means that if the announce matches this filter it is
+passed onto the user. See HELP FILTERS for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+
+You can use any of the following things in this line:-
+
+
+
+
+This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+
+
+
+
+Create an 'reject this spot' line for a filter.
+
+An reject filter line means that if the spot matches this filter it is
+dumped (not passed on). See HELP FILTERS for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+
+You can use any of the following things in this line:-
+
+
+
+
+This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+
+
+
+
+It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+
+
+
+
+This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+
+ reject/wcy gb7djk all
+
+
+
+
+It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+
+
+
+ This version allows a sysop to set a filter for a callsign as well as the
+default for nodes and users eg:-
+
+
+
+
+You can reply to a message and the subject will automatically have
+"Re:" inserted in front of it, if it isn't already present.
+
+You can also use all the extra qualifiers such as RR, PRIVATE,
+NOPRIVATE, B that you can use with the SEND command (see SEND
+for further details)
+
+
+
+
+All the SEND commands will create a message which will be sent either to
+an individual callsign or to one of the 'bulletin' addresses.
+
+SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
+it will mark the message as personal and send it to the cluster node that
+that callsign is connected to.
+
+You can have more than one callsign in all of the SEND commands.
+
+You can have multiple qualifiers so that you can have for example:-
+
+
+
+
+Literally, record your address details on the cluster.
+
+
+
+
+Allow announce messages to arrive at your terminal.
+
+
+
+
+Set the node_call as an AR-Cluster type node
+
+
+
+
+Setting a callsign as a 'badnode' will prevent spots from that node
+going any further. They will not be displayed and they will not be
+sent onto other nodes.
+
+The call can be a full or partial call (or a prefix), eg:-
+
+
+
+
+Add a beep to DX and other terminal messages.
+
+
+
+
+Set the node_call as a CLX type node
+
+
+
+
+You can remove this level with unset/debug <name>
+
+
+
+
+You can stop DX messages with the unset/dx command
+
+
+
+
+Some logging programs do not like the additional information at
+the end of a DX spot. If this is the case, use the unset/dxgrid
+command to remove the grid squares.
+
+
+
+
+Set the node_call as a DXNet type node
+
+
+
+
+If you are connected via a telnet session, different implimentations
+of telnet handle echo differently depending on whether you are
+connected via port 23 or some other port. You can use this command
+to change the setting appropriately.
+
+You can remove the echo with the unset/echo command
+
+The setting is stored in your user profile.
+
+YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
+
+
+
+
+Let others on the cluster know you are here by only displaying your
+callsign. If you are away from your terminal you can use the unset/here
+command to let people know you are away. This simply puts brackets
+around your callsign to indicate you are not available.
+
+
+
+
+Tell the cluster system where you normally connect to. Any Messages sent
+to you will normally find their way there should you not be connected.
+eg:-
+
+
+
+
+Set the hop count for a particular type of broadcast for a node.
+
+This command allows you to set up special hop counts for a node
+for currently: announce, spots, wwv and wcy broadcasts.
+
+
-Works just like the user command except that sysops can see ALL messages.
+
+
+Connect a node to your system in such a way that you are a full protocol
+member of its network and can see all spots on it, but nothing either leaks
+out from it nor goes back into from the rest of the nodes connected to you.
+
+You can potentially connect several nodes in this way.
+
+You can see which nodes are isolated with the show/isolate (1) command.
+
+You can remove the isolation with the command unset/isolate.
+
+
-
-Disconnect any <call> connected locally
+You can select the language that you want the cluster to use. Currently
+the languages available are en (English) and nl (Dutch).
-
-
-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).
+You can set your latitude and longitude manually or alternatively use the
+set/qra command which will do the conversion for you.
-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:-
+
-
-This command sends out any information held in the user file which can
-be broadcast in PC41 protocol packets. This information is Name, QTH, Location
-and Homenode. PC41s are only sent for the information that is available.
+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:-
-
-
-This command attempts to re-initialise a link to a (usually) AK1A node
-that has got confused, usually by a protocol loop of some kind. It may
-work - but you usually will be better off simply disconnecting it (or
-better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
-node>).
+Show users and nodes when they log in and out of the local cluster. You
+can stop these messages by using the unset/logininfo command.
-Best of luck - you will need it.
-