I am having a lot of difficulty reading the detailed logs from gnugk. When making test calls, it is ok, but when gnugk is in production I get 1Gb of logs per day. Searching through a 1GB file is hard, but then there is the other problem: the calls overlap, so I don't know exactly where a log portion is from the call I am interested in or not. Is there a way to mark the h323 packets with the call number or anything like that, so that the logs are more easy to read. Ideally (although I have no idea how this should be done) one could grep the log file with a specific pattern and get the logs for a certain call. ------------------------- E-Mail powered by MadNet. http://www.madnet.ro/ ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r _______________________________________________________ Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id?49 Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users Homepage: http://www.gnugk.org/
