I have over 90 systems connected to a GnuGK which runs as a proxy to the internet. I often get calls which fail, but because the gk_trace.log file tracks everything, it becomes impossible to follow the "thread" of a call setup because there doesn't seem to be a way to filter out just one particular call; so troubleshooting means trying to determine if a particular message in the log file is for some other call, a valid RCF, etc. How do people with larger configurations perform the troubleshooting and log analysis? Jan, is there some way to have GnuGK create a separate log file for each registered endpoint, and then just have gk_trace.log hold "everything else" and housekeeping? Or if the log file tracked which endpoint_id a particular log entry related to then it would be easy to grep. ------------------------------------------------------------------------------ Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev _______________________________________________________ Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx 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/
