Text 2057, 43 rader
Skriven 2004-07-13 15:06:26 av mark lewis (1:3634/12)
   Kommentar till text 2049 av Sean Dennis (1:11/200)
Ärende: IPN nodes and BT
========================
 ml>> dial those numbers... [geez, what a sentenence]... this is why i what
 ml>> i was saying earlier about having two instances looking at two
 ml>> different nodelist compilations since it is apparent that only one at
 ml>> a time can be active... that is, unless bink on the IP side can remove
 ml>> the IPN and dial the rest of the number ;)

 SD> I don't know if you can tell two instances to use a seperate
 SD> nodelist-all instances use the same config files.  I'll tinker
 SD> with it and see if I can.

by two instances, i'm meaning two completely seperate ones that use different
configs... the only thing shared would possibly be the inbound and outbound
directories... the nodelist settings and directories would definitely have to
be different...

this reminds me of way back when when one was able to force frontdoor into a
multinode setting with a few minor problems... at that time, FD was not
multinode capable or aware and the instances did not talk to each other via
semaphores like they do today...

the way i (currently) get around this nodelist situation in multinode FD is to
use environment variables... FD, the nodelist processor FDNC and the FDNODE.CTL
file all recognise the environment variables... this is how i (currently)
override the contact number and its a task that i detest...

i have two "control files" that contain settings for each system i override for
IP telnet connections... one control file contains the existing nodelisted POTS
number if one exists... the other control file contains the IP number or the
domain name... only one of these control files is used on each node/instance
and that is determined by whether the node/instance is POTS or IP capable...

thus when i look at the entry from a POTS instance, i'll see the POTS number...
when i look at the same entry from an IP instance, i'll see the domain or IP
number...

this also requires that i have a coupld of other files that are seperate
between nodes/instances but FD is designed with this in mind and i don't see it
as all that difficult to manage, really... one just has to remember to set all
the settings in all the nodes/instances that do not use the default settings...

)\/(ark

 * Origin: (1:3634/12)