Maybe trace leve 6 log when the reload command is issued will show, which section loads so long. There are timestamps in the log, so it may be possible to find out the problem.
----- Original Message ----- From: "Jiří Gubík" <[EMAIL PROTECTED]> Sent: Friday, June 29, 2007 7:09 PM > Hi, > we are using kill - HUP for reload:-) > > For Michal: > I tested reload on gatekeeper without any load just with one registered > gateway. There was no call before, during and after reload. Billing > backend is on same PC. Reload is taking on this machine same time as in > production environment - almost one minute. > The problem is really with routing tables. We have more than 25 > gatekeepers configured as neighbor. On each gatekeeper is registered up > to 300 gateways and terminals, each one with separate number. This mean > a lot of entries in [RoutingPolicy] and [Neighbor::xxxx] sections. > Config files are generated from SQL, and they are distributed to all > gatekeepers by script at same time. > I need to add more entries to config. And I am looking some solution. > Is routing by virtual queue only solution? > Thanks > Jiri ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________________ Posting: mailto:[email protected] Archive: http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-users Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users Homepage: http://www.gnugk.org/
