[Dxspider-support] Two problems with crontab?

[Ron Gibson]

Hi David,
I'm also looking forward to the answer. I reported this issue a couple 
years ago. I ended up doing all the spawn stuff via the crontab on my 
linux box.
73 de Ron
VE3CGR

On 11/11/2013 8:14 PM, David Spoelstra wrote:
> In trying to debug my previous issue I reduced everything to the
> minimum and came across two issues:
>
> Here's my /spider/local_cmd/crontab:
> # min, hour, day-of-month, month, day-of-week (0=Sun) command
> # Connect to other nodes
> * * * * * start_connect('w9zrx') unless connected('w9zrx')
> * * * * * start_connect('k9usa') unless connected('k9usa')
> 03 01 * * * spawn("/usr/bin/touch /tmp/n9kt")
>
> Here's what I see in watchdbg:
> 01:03:00 cron: 3 1 12 11 2 -> doing 'start_connect('w9zrx') unless
> connected('w9zrx')'
> 01:03:00 cron: 3 1 12 11 2 -> doing 'start_connect('k9usa') unless
> connected('k9usa')'
> 01:03:00 cron: 3 1 12 11 2 -> doing 'spawn("/usr/bin/touch /tmp/n9kt")'
> 01:03:00 spawn of /usr/bin/touch /tmp/n9kt started
> 01:03:00 -> D W9ZRX PC17^N9KT^N9KT-2^H25^
> 01:03:00 DXCommand
> 01:03:00 N9KT disconnected
> 01:03:00 DXChannel N9KT destroyed (5)
> 01:03:01 -> D W9ZRX PC21^WA9PIE-2^Gone^H25^
> 01:03:01 -> D K9USA PC92^N9KT-2^3780^D^^5WA9PIE-2^H99^
> 01:03:01 DXChannel WA9PIE-2 destroyed (4)
> 01:03:01 DXChannel K9USA destroyed (3)
>
> First issue:  This really ran at 8:03pm local (EDT)!  So are the times
> in the DXSpider crontab really GMT?
>
> Second issue:  The spawn command seemed to kill off my two node
> connections!  This doesn't happen if I comment out the spawn command.
>
> What am I doing wrong?
>
> Thanks!
> -David
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at dxcluster.org
> http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
>