- 1. Installation
+ \e[1m1. Installation\e[0m
- 1.1. Where do I get DXSpider?
+ \e[1m1.1. Where do I get DXSpider?\e[0m
All things Spider can be found at www.dxcluster.org and the actual
program and patches can be found in the download area.
- 1.2. How do I use the patches?
+ \e[1m1.2. How do I use the patches?\e[0m
Patching is done in the standard linux way ...
first need to apply patch-1.39 and then patch-1.40.
- 1.3. If I use a tarball to overwrite my installation, what happens to
- my configuration?
+ \e[1m1.3. If I use a tarball to overwrite my installation, what happens to\e[0m
+ \e[1mmy configuration?\e[0m
The tarballs are designed to not overwrite your existing configuration
and can be used at any time to update your Spider software. All the
key files have the suffix .issue (eg. DXVars.pm.issue) at default.
- 1.4. I am running RedHat 5.2 and I am getting strange errors, what is
- wrong?
+ \e[1m1.4. I am running RedHat 5.2 and I am getting strange errors, what is\e[0m
+ \e[1mwrong?\e[0m
The version of Perl that comes with 5.2 seems to be some kind of pre-
release and is broken. You can get a new version of perl from
it with the CPAN modules.
- 2. Administration
+ \e[1m2. Administration\e[0m
- 2.1. How can I get Spider to restart automatically if it crashes?
+ \e[1m2.1. How can I get Spider to restart automatically if it crashes?\e[0m
Put this line into /etc/inittab ..
- Run telinit q as root. Spider will restart so be aware. However, any
+ Run \e[4mtelinit\e[24m \e[4mq\e[24m as root. Spider will restart so be aware. However, any
time you reboot, cluster.pl will start in tty7 and if it crashes, it
should restart ok.
- 2.2. How can I monitor traffic to and from a node or user?
+ \e[1m2.2. How can I monitor traffic to and from a node or user?\e[0m
- There are 2 ways to achieve this. You can use the tail command like
+ There are 2 ways to achieve this. You can use the \e[4mtail\e[24m command like
this ..
- or in later versions of Spider, there is a command called watchdbg in
+ or in later versions of Spider, there is a command called \e[4mwatchdbg\e[24m in
which case you simply type ..
- 2.3. My neighbouring node cannot use the RCMD command to me, he just
- keeps getting the "tut tut" message.
+ \e[1m2.3. My neighbouring node cannot use the RCMD command to me, he just\e[0m
+ \e[1mkeeps getting the "tut tut" message.\e[0m
Assuming that the permissions are set correctly (perm level 5
required), it could be that the home_node is set incorrectly. You can
- reset the home_node using the spoof command like this ..
+ reset the home_node using the \e[4mspoof\e[24m command like this ..
Assuming that the node_call you are changing is gb7adx.
- 2.4. I do not seem to be sending any bulletin mail to my link part-
- ners, what is wrong?
+ \e[1m2.4. I do not seem to be sending any bulletin mail to my link part-\e[0m
+ \e[1mners, what is wrong?\e[0m
There is a file in /spider/msg called forward.pl.issue. Rename this
to forward.pl and edit it to meet your requirements. You will need to
- issue the command load/forward or restart Spider for the changes to
+ issue the command \e[4mload/forward\e[24m or restart Spider for the changes to
take effect.
- 2.5. How can I automatically limit the amount of debug logfiles that
- are stored?
+ \e[1m2.5. How can I automatically limit the amount of debug logfiles that\e[0m
+ \e[1mare stored?\e[0m
Use the tmpwatch command. Create a file in /etc/cron.daily/
containing the line ...
This will limit your debug data down to the last 10 days
- 2.6. I updated my Linux distribution and now Spider cannot read the
- users file or the dupefile, what is the problem?
+ \e[1m2.6. I updated my Linux distribution and now Spider cannot read the\e[0m
+ \e[1musers file or the dupefile, what is the problem?\e[0m
Almost certainly this is a change in the db format of perl. Follow
these few steps to correct the problem.
That should solve the problem.
- 2.7. Since I last updated I seem to be getting duplicate spots
- appearing.
+ \e[1m2.7. Since I last updated I seem to be getting duplicate spots\e[0m
+ \e[1mappearing.\e[0m
What has probably happened is that the dupefile has got corrupted in
some way. Simply delete the /spider/data/dupefile and restart the
should solve your problem.
- 2.8. I have deleted a message but it is still there, why?
+ \e[1m2.8. I have deleted a message but it is still there, why?\e[0m
This is now the way messages are handled for deletion in Spider. If
you look closely you will see a 'D' following the message number.
This message is marked for deletion and will be deleted in 2 days if
nothing further is done. Optionally you can use the command
- delete/expunge to delete it immediately.
+ \e[4mdelete/expunge\e[24m to delete it immediately.
projects / spider.git / blobdiff