X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=sgml%2FspiderFAQ_en.sgml;h=4e93d269271d54b5ffa4b9da361e6d0e916ca83c;hb=refs%2Fheads%2Fnew-spawn;hp=2ebda13e0951d36885ce06ae551858aa16205cbd;hpb=0fcb7df9b5f6b17605f07d965e71d8bc4dee09a0;p=spider.git diff --git a/sgml/spiderFAQ_en.sgml b/sgml/spiderFAQ_en.sgml index 2ebda13e..4e93d269 100644 --- a/sgml/spiderFAQ_en.sgml +++ b/sgml/spiderFAQ_en.sgml @@ -6,7 +6,7 @@ The DXSpider FAQ Ian Maude, G0VGS, (g0vgs@gb7mbc.net) -December 2001 Revision: 1.8 +February 2005 Revision: 1.8 A reference for SysOps of the DXSpider DXCluster program. @@ -48,7 +48,7 @@ to apply patch-1.39 and then patch-1.40.

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. +files have the suffix .issue (eg. DXVars.pm.issue) at default. I am running RedHat 5.2 and I am getting strange errors, what is wrong? @@ -89,6 +89,26 @@ case you simply type .. watchdbg G0VGS +I see spots coming in my debug log, but none go out to the users + +

+Please check the time on your PC. + +

+All spots are checked that they are no more +than 15 minutes in the future and 60 minutes in the past. If your clock on your client +prompt (or console.pl display) is not set to the correct time +in GMT (UTC) and is more than one hour out (say on your local (summer) time) then +the test will fail and no spots will come out. Neither will they be stored. + +

+If you are connected to the internet, most linux distributions have an implementation of +. The Microsoft Windows 2003, XP, +2000 and NT machine clock can also be set to be syncronised +to an NTP source. This can be done in the standard time configuration screen. There is also +the simple program for Windows 95/98/ME. + + My neighbouring node cannot use the RCMD command to me, he just keeps getting the "tut tut" message. @@ -122,7 +142,9 @@ Use the tmpwatch command. Create a file in /etc/cron.daily/ containing the line Remember to make it executable! -This will limit your debug data down to the last 10 days +This will limit your debug data down to the last 10 days. + +However, modern versions of DXSpider will do this for you, so this is now probably unnecessary. I updated my Linux distribution and now Spider cannot read the users file or the dupefile, what is the problem? @@ -133,7 +155,7 @@ few steps to correct the problem. stop the cluster (disable any autostart in inittab) cd /spider/data -issue the command perl user_asc +issue the command: perl user_asc restart the cluster @@ -156,4 +178,96 @@ 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. +I have updated from CVS and I get all sorts of errors when I restart + +

+Whenever you update from CVS, a log is displayed. Next to each +file that is downloaded there is a letter, e.g.: + + +? fred.pl +? jim +.. +. +.. +cvs server: Updating perl +P cluster.pl +C Messages +M Internet.pm +U DXProt.pm +.. +. +.. + + +

+For normal CVS use you should only ever see the letters 'P', 'U' or '?'. The +letter 'P' means that the file has +changed in CVS and is more recent than the one that is currently on your system. You will also +see the letter '?', which means that +there is a file that you (or the system) has created that CVS doesn't know about and isn't +under its control. These are all normal and good. + +

+Sometimes you will see the letter 'U' next to a file. This means that it is a new file that you don't currently +have. This is also OK. + +

+However, if you see the letter 'C' or 'M', that means that CVS thinks that the file has +changed locally. For the letter 'C', it has changed sufficiently near to one or more +modifications which CVS wants to download to your system. For the 'M', CVS thinks that it +is OK to make the change (you may also see some messages about "merging revision 1.xx with 1.yy"). +Neither of these things are good. Files that are under the control of CVS +must not be changed by sysops. It is the files that have the 'C' next to them that will show +the errors that you are complaining about and they will be things like:- + + +Syntax error near '<<<<' at line 23 +Syntax error near '===' at line 40 +Syntax error near '>>>' at line 51 + + +

+You will not necessarily see all of the errors shown but you will get one or more sets of some +of them. The cure is simple: + + + identify the file that is causing the problem. + remove the file. + run the cvs update again. + + +

+You will see that file come back (with a letter 'U' next to it). That will be the correct +file as CVS thinks it should be. If you still have a problem, then get onto the +dxspider-support mailing list. + +

+If all else fails (or you have several conflicts) you can safely remove the entire /spider/perl and +/spider/cmd directories and then run the cvs update. They will all be recreated in their pristine +condition. + +I have done a CVS update, restarted and it says that "fileX" is missing + +

+The correct way to run cvs is:- + + +cd /spider +cvs -z3 update -d + + +

+The '-d' is crucial. It makes sure that any new directories, that may contain new code, +are created and that new code downloaded. I have absolutely no idea why this is not the +default, seeing as CVS (in other circumstances) happily recurses its merry way down a +directory tree, but there you are. + +

+WinCVS and other graphical CVS frontends have a checkbox for the update screen called something +like "create sub-directories" (it may be hidden in some sub-screen - go look for it if it isn't +obvious). Make sure that this box is checked. If you can make this the +default setting in the program's setup screen then please do that. It will save you a lot +of pulled hair. +