Maybe trace leve 6 log when the reload command is issuedwill show, which section loads so long. There are timestampsin the log, so it may be possible to find out the problem. ----- Original Message ----- From: "Jiří Gubík" <jgubik@xxxxxxxxxxx>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 ExpressDownload DB2 Express C - the FREE version of DB2 express and takecontrol of your XML. No limits. Just data. Click to get it now.http://sourceforge.net/powerbar/db2/_______________________________________________________ Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxxxxxxxxx: http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-usersUnsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-usersHomepage: http://www.gnugk.org/
