I can understand the reason - the risk of HUGE logs is nasty - it is only in situations like this where you have an amatuer who can't hack the code properly himself coupled with an intermitant problem that he can't reproduce that it becomes an issue.
Thanks for making the change (and confirming that I wasn't going mad) - is there a change log kept anywhere so that I can keep track of whats changing without polluting the list with my questioning? Again thanks Kevin -----Original Message----- From: Fritz Borgstedt [mailto:f...@iworld.de] Sent: 07 April 2009 15:38 To: ASSP development mailing list Subject: Re: [Assp-test] 1.5.1.2 - Many Connection Idle - timeout ASSP development mailing list <assp-test@lists.sourceforge.net> schreibt: >if there is a way to make the log remain >longer I would be glad of the secret. Obviously it was a bad idea to have only 5 minutes debugging files. Sorry. I removed that in the newest version. ------------------------------------------------------------------------ ------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
