X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fcron.html;h=d4f82f46b81d858f8e852af1608ee76c59ab7a5c;hb=a5b87707adf1ba8e43fad6f2f74aa74fb1952d27;hp=596e72e516726852a8de15b3b1db83fa4963f4ea;hpb=5d197c9f7aa2ea796d86aa5473f93956b24cf1b7;p=spider.git diff --git a/html/cron.html b/html/cron.html index 596e72e5..d4f82f46 100644 --- a/html/cron.html +++ b/html/cron.html @@ -2,11 +2,12 @@
-Last modified: Mon Dec 28 23:19:21 GMT 1998 +Last modified: Mon Apr 23 01:00:44 BST 2001
+ start_connect('gb7tlh') unless connected('gb7tlh') ++ this could have also been written: +
start_connect('gb7tlh') if !connected('gb7tlh')- will attempt to start a connection process to GB7TLH if it isn't + but the first method is more 'perlish', +
Either of these commands will attempt to start a connection process to GB7TLH if it isn't already locally connected.
There is absolutely no reason why you could not do something more complicated using information @@ -92,7 +98,7 @@ Last modified: Mon Dec 28 23:19:21 GMT 1998 # check every 10 minutes to see if gb7tlh is connected and if not # start a connect job going - 0,10,20,30,40,50 * * * * start_connect('gb7tlh') if !connected('gb7tlh') + 0,10,20,30,40,50 * * * * start_connect('gb7tlh') unless connected('gb7tlh') # at 03:15 on Sundays start a job called 'analyse.pl' which does something # or other. This starts a new process and runs to completion, be careful @@ -106,12 +112,32 @@ Last modified: Mon Dec 28 23:19:21 GMT 1998 # the values for mycall and version 15,30 * * * spawn("echo $main::mycall is a DXSpider Version $main::version DX Cluster system") + + # then there is always the highly contentious one like this little jem which + # checks every hour to see if a certain callsign is connected to another cluster + # and silently disconnects him. This is an example only (of course...) + + 23 * * * * rcmd('rcmd/gb7dxm disc/noinform G9TLH') if present_on('G9TLH', 'GB7DXM') + + # some people like to do an hourly announce to say who they are. There is a + # slight complication about this because of the announce duplicate checking + # so you need to make each announce unique. I do this by adding a date and time + # stamp on the end + + 0 * * * * run_cmd('ann CLUSTER: GB7DJK JO02LQ at ' . cldate . ' ' . ztime) + It is important remember that these crontab routines execute in line with the main - cluster code, so if you create a long, slow crontab commands, it will impact on the speed + cluster code, so if you create a long, slow crontab command, it will impact on the speed and usability of the cluster as a whole. +
If you want to see what commands are being run and/or the syntax errors in the + crontab, then run: set/debug cron on the console and monitor the + debuging output (I use watchdbg in another window). + +
To set the debugging back to normal do: unset/debug cron. +
I believe this now to be fixed. YMMV, if so tell me about it! -