[arm-allstar] Cron Job

[Doug Crompton]

Pierre,

  We will look at the Echolink code but I will repeat again that Echolink is an add-on basically intended for users to connect for a short amount of time to converse with allstar users. It does not have a permanent connect option nor is it intended for a permanent connection. Any disruption in the circuit would cause a disconnect unlike a permanently connected Allsar node. We are working on many improvements to Allstar but Echolink is not at the top of the list.

I also would say that the database problem is probably outside of Allstar.. I run a hub here on the same code running Echolink that never loses its database and it has uptimes of months or more.
73 Doug
WA3DSP
http://www.crompton.com/hamradio


Date: Sun, 10 Jul 2016 06:25:20 -0400
Subject: Re: [arm-allstar] Cron Job
From: petem001 at gmail.com
To: arm-allstar at hamvoip.org
CC: doug at crompton.com

The cron tab thing is a nice fix, but it is not a real solution.
I am in the same situation as the OP.
never had a stable Echolink database.
I would think thst it would be possible to trigger a full database dowbload in ome way when there is 2 unautorized connection from the same Ip or node number in a 90 second span? 
or a fix full reload every 4 hours? this would help a lot.
I have 2 node connected all the time and astres.sh redo the connection and Alison start announcing all those message every time. And I have user on the repeater all night long. 

 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160710/aca20377/attachment.html>