> Have you been getting my email? I just want to know if a fix is possible
> or should I just toss in the towel.
I have received two messages from you saying this:
> Can you tell me what generates the following message in io.lo:
> Nov 29 05:26:28 ihs1 syslog: icl_com/clx_rte.cc: Timeout for k4uj route 0.
> If I can find this out, I can fix my problem.
I don't know much more so it's difficult to make a statement.
icl_com starts up your connect script and then waits a specific amount
of time for the connection to succeed (i.e. a PC18 must be seen). If
that doesn't arrive the script is timed out and a message such as
the one above is generated. This is apart from what you are doing
"inside" the script.
Currently (v4.02) there is no way to control the timing of a script.
When using the route information in cluster_par with (a) or (w)
type, you can set the timeout with the %%% syntax. With a script
(x) you cannot. We might change this in the future, but it's not
really a hot topic on the To-Do-List.
Why exactly would you need to modify the timeout value? How
long does it actually take your script to build up the connection?
Can you post the script you are using? Is the script working
when you test it from a tty (not via icl_com but by calling it
from the command line)?
Please post or CC: our conversation to the CLX reflector for others
to read.
73 Ben
--
[] clx - PacketCluster Software for Linux
[] c/o Bernhard ("Ben") Buettner, DL6RAI
[] Internet: xokxo.tirdtpkzrf@bom.gov.au
[] Packet: DL6RAI @ DB0AAB.#BAY.DEU.EU