(RADIATOR) recommended method to "event notify" radiator to a restart/reread

[Tariq Rashid]

hi - i'm sire many of you have come across this issue before, and its not
unique to radiator either.

the radius clients can be kept in the radius.cfg file (as <Client, 1.2.3.4>
for example) or in a database, and i'm sure they can be kept in other
locations too ...

however, when an external system updates this list, either by rewritring the
radius.cfg file, or updating an included file, or by adding entries to or
removing entries from an sqlclientlist database ... a running radiator does
not take account of the changes until the radiator server instances if
restarted or sent a -HUP signal. 

is there a recommended way to do this from remote locations? that is, these
event notification originate on different machines to those which are
actually running the server instances. 

i want to avoid additional custom written "event notification and restart"
software as it adds points of weakness into an otherwise solid system, and
also requires additional support. (its is for this reason that i want to
avoid external sql databases too, as that requires additional support and a
more complex set of failure points)

a not-so-good solution is to perhaps ask radiator to restart/reHUP
periodically. i don't think there is a "file-watching" mechanism in
radiator?

tariq

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.