CLX archive - 1998: Re: cluster_par changes

Re: cluster_par changes

Franta Bendl (tnh@voicenet.com)
Mon, 10 Aug 1998 10:26:26 +0200

--------------C2FEC6E79C9CC004A2CF418C
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Matthew George wrote:

> Are there changes that can be made to cluster_par that require a
> 're-start' in version 4.0 of CLX? Or are ALL changes re-read dynamically
> with no need to 're-start' CLX?
>
> I think I remember reading somewhere that some changes require a
> 're-start', if so, what changes require a 're-start'?
>
> mg
>
> --
> Matthew George
> mailto:dtgpu.jyrmryiiac@blancmange.org
> mailto:emhtmne@mailit.tunk.net
> NG7M

hi matthew,

all the parameter in cluster_par don't require restart of clx. it will be
checked every 5 minutes and the changes are immediataly active with
exception of deleted cluster. if you delete a cluster (deletion of whole
SECTION or you change the call in a SECTION) from cluster_par and the
connection to this cluster is up, it will deleted first after the next
disconnect
(you have the possibility to disconnect it immediately using clx_adm).

a little bit other is the situation for clx_par. you will need the restart
of clx if you want change one of the following parameters:
call, ssid
db_name, db_port, db_host
prot,
callb
wampes, ax25, w_host.
all other parameters will be changed online (also after about 5min).

73 de franta

P.S.: in the recent version V400 is a bug. the parameter conn_ping is not
working. but if you write the first character for parameter protocoll
conn_prot as upper case it has same effect as conn_ping:n (other bug, hi).

--------------C2FEC6E79C9CC004A2CF418C
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

Matthew George wrote:

Are there changes that can be made to cluster_par that require a
're-start' in version 4.0 of CLX? Or are ALL changes re-read dynamically
with no need to 're-start' CLX?

I think I remember reading somewhere that some changes require a
're-start', if so, what changes require a 're-start'?

mg

--
Matthew George
mailto:kwmcmla.jtyanw@nsw.gov.au
mailto:pvbwtlyc@tdinfo.com
NG7M

  hi matthew,

all the parameter in cluster_par don't require restart of clx. it will be checked every 5 minutes and the changes are immediataly active with exception of deleted cluster. if you delete a cluster (deletion of whole SECTION or you change the call in a SECTION) from cluster_par and the connection to this cluster is up, it will deleted first after the next disconnect
(you have the possibility to disconnect it immediately using clx_adm).

a little bit other is the situation for clx_par. you will need the restart of clx if you want change one of the following parameters:
call, ssid
db_name, db_port, db_host
prot,
callb
wampes, ax25, w_host.
all other parameters will be changed online (also after about 5min).

73 de franta

P.S.: in the recent version V400 is a bug. the parameter conn_ping is not working. but if you write the first character for parameter protocoll conn_prot as upper case it has same effect as conn_ping:n (other bug, hi).
 
  --------------C2FEC6E79C9CC004A2CF418C--