Hi everybody, GnuGk has been checking the config file for misspellings for quite a while now, but people seem to miss the error messages or simply ignore them. GnuGk 3.6 now has a command line option --strict that prevents GnuGk from starting as long as you have errors in your config and I would urge everybody to switch this on during all testing. It saves you a lot of surprises later on. I was tempted to make this the default behavior, but when you make a config change on a busy server, and you need to restart it quickly, you don't want it to go out of service, because of a small typo. So its up to you t use --strict at least when you are preparing a new config in the lab or switch it always on to avoid surprises. Regards, Jan -- Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.gnugk.org/ ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________________ 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/
