X-Git-Url: http://gb7djk.dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2FspiderFAQ-2.html;fp=html%2FspiderFAQ-2.html;h=0000000000000000000000000000000000000000;hb=7d315a555a73d4a650405d0c2da48bacde2b1853;hp=4f15b247e157c39c4c43b71859a7e28d65f7a4af;hpb=1bb3ae1a09a6117d93c02041bff9b5cd2d4819ef;p=spider.git diff --git a/html/spiderFAQ-2.html b/html/spiderFAQ-2.html deleted file mode 100644 index 4f15b247..00000000 --- a/html/spiderFAQ-2.html +++ /dev/null @@ -1,126 +0,0 @@ - - - - - The DXSpider FAQ: Administration - - - - - -Next -Previous -Contents -
-

2. Administration

- -

2.1 How can I get Spider to restart automatically if it crashes? -

- -

Put this line into /etc/inittab ..

-

-

-
-DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop > /dev/tty7
-
-
-

-

Run telinit q 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? -

- -

There are 2 ways to achieve this. You can use the tail command like this ..

-

-

-
-tail -f /spider/data/debug/167.dat |grep G0VGS
-
-
-

-

or in later versions of Spider, there is a command called watchdbg in which -case you simply type ..

-

-

-
-watchdbg G0VGS
-
-
-

- -

2.3 My neighbouring node cannot use the RCMD command to me, he just keeps getting the "tut tut" message. -

- -

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 ..

-

-

-
-spoof gb7adx set/home gb7adx
-
-
-

-

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 partners, what is wrong? -

- -

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 -take effect.

- -

2.5 How can I automatically limit the amount of debug logfiles that are stored? -

- -

Use the tmpwatch command. Create a file in /etc/cron.daily/ containing the line ...

-

-

-
-/usr/sbin/tmpwatch -f 240 /spider/data/debug
-
-
-

-

Remember to make it executable!

-

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? -

- -

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. -

- -

What has probably happened is that the dupefile has got corrupted in -some way. Simply delete the /spider/data/dupefile and restart the -cluster. It may take a little time to become fully functional but -should solve your problem.

- -

2.8 I have deleted a message but it is still there, why? -

- -

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.

- -
-Next -Previous -Contents - -