RE: stdout.log file growing very quickly.
Howdy, >tomcat 4 as well, or just 5? If so, then presumably there is a logging >properties config file somewhere, which the original poster could >configure so that less output goes to the console? Tomcat 4 to a lesser extent than tomcat 5. You can add a configuration file if you wish to customize logging. You can put it in $CATALINA_HOME/server/classes or /common/classes so that it affects tomcat. >I must either stop trying to do so much or be more efficient at what I >am doing before I can launch into helping at tomcat. But it would be >nice to take part. I am actually contributing patches at ant, but they >seem to have hordes of people contributing diverse patches which they >(seem to imho) wish they didn't have. Guess it's the broad nature of >ant's functionality. I feel pretty safe saying tomcat doesn't have the same problem. Just make sure to properly categorize your patch as an enhancement. I can't speak for other developers, but for one get annoyed (and therefore less likely to act upon) a minor enhancement request submitted as a "Blocker" severity level issue ;) Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: stdout.log file growing very quickly.
On 09/22/2003 04:25 PM Shapira, Yoav wrote: Tomcat is already mostly switched over to commons logging. tomcat 4 as well, or just 5? If so, then presumably there is a logging properties config file somewhere, which the original poster could configure so that less output goes to the console? In that case, this 'swallowOutput' attribute, that causes output to be directed to the daily logs, will cause many log entries to be duplicated in that log? Some things are still controlled by the debug attributes in server.xml. Setting all those to zero will not make tomcat completely silent. You're welcome to contribute patches to convert remaining parts of tomcat to use commons-logging. I must either stop trying to do so much or be more efficient at what I am doing before I can launch into helping at tomcat. But it would be nice to take part. I am actually contributing patches at ant, but they seem to have hordes of people contributing diverse patches which they (seem to imho) wish they didn't have. Guess it's the broad nature of ant's functionality. Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: stdout.log file growing very quickly.
Howdy, >another question on this topic which has long puzzled me: is tomcat >being changed over to commons-logging to output log statements? It would be good to start a different mailing list thread when you have a different (albeit related) question ;) >Or is it all configured going to remain controlled by the debug >attributes of nodes in server.xml? > >If I set all those debug attributes to "0", will tomcat become totally >silent? Tomcat is already mostly switched over to commons logging. Some things are still controlled by the debug attributes in server.xml. Setting all those to zero will not make tomcat completely silent. You're welcome to contribute patches to convert remaining parts of tomcat to use commons-logging. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: stdout.log file growing very quickly.
another question on this topic which has long puzzled me: is tomcat being changed over to commons-logging to output log statements? Or is it all configured going to remain controlled by the debug attributes of nodes in server.xml? If I set all those debug attributes to "0", will tomcat become totally silent? Adam On 09/22/2003 03:43 PM Shapira, Yoav wrote: Howdy, Why is it growing so fast? You have several options, all of which have been discussed on the list in the past. They include: - Using an external program like logrotate to rotate the stdout log for you. - Adding swallowOutput="true" to your context so that stdout/stderr output from those webapps goes to their servlet log, which tomcat rotates for you nightly. Yoav Shapira Millennium ChemInformatics -Original Message- From: Wood, Daniel [mailto:[EMAIL PROTECTED] Sent: Monday, September 22, 2003 7:24 AM To: '[EMAIL PROTECTED]' Subject: stdout.log file growing very quickly. Hello, We're using Tomcat 4.1 and we have a problem where the logs\stdout.log grows very quickly. I was wondering if you had any advice to offer? What would be ideal is if we could have the properties of org.apache.catalina.logger.FileLogger to create a new log every new day. I've searched the internet, and could not find anything about stdout.log and this problem, other than to keep clearing the file down manually. Thanks in advance. Dan. EMAIL DISCLAIMER Please Note: The information contained in this message may be privileged and confidential, protected from disclosure, and/or intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying or other dissemination of this communication is strictly prohibited. If you received this communication in error, please immediately reply to the sender, delete the message and destroy all copies of it. Thank You This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- struts 1.1 + tomcat 4.1.27 + java 1.4.2 Linux 2.4.20 RH9 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: stdout.log file growing very quickly.
Howdy, Why is it growing so fast? You have several options, all of which have been discussed on the list in the past. They include: - Using an external program like logrotate to rotate the stdout log for you. - Adding swallowOutput="true" to your context so that stdout/stderr output from those webapps goes to their servlet log, which tomcat rotates for you nightly. Yoav Shapira Millennium ChemInformatics >-Original Message- >From: Wood, Daniel [mailto:[EMAIL PROTECTED] >Sent: Monday, September 22, 2003 7:24 AM >To: '[EMAIL PROTECTED]' >Subject: stdout.log file growing very quickly. > >Hello, > >We're using Tomcat 4.1 and we have a problem where the logs\stdout.log >grows >very quickly. > >I was wondering if you had any advice to offer? > >What would be ideal is if we could have the properties of >org.apache.catalina.logger.FileLogger >to create a new log every new day. > >I've searched the internet, and could not find anything about stdout.log >and >this problem, other than to keep clearing the file down manually. > >Thanks in advance. > >Dan. > > > > > > > > > > > > > > >EMAIL DISCLAIMER > >Please Note: The information contained in this message may be privileged >and >confidential, protected from disclosure, and/or intended only for the use >of >the individual or entity named above. If the reader of this message is not >the intended recipient, or an employee or agent responsible for delivering >this message to the intended recipient, you are hereby notified that any >disclosure, distribution, copying or other dissemination of this >communication is strictly prohibited. If you received this communication in >error, please immediately reply to the sender, delete the message and >destroy all copies of it. > >Thank You This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]