RE: [JBoss-dev] Why are we using RollingFileAppender in RH?
I mind if you switch it over because we'll forget to switch it back after JBoss 3.0 goes GA. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jason Dillon Sent: Saturday, December 29, 2001 2:51 PM To: David Budworth; [EMAIL PROTECTED] Subject: Re: [JBoss-dev] Why are we using RollingFileAppender in RH? Can we set it to roll on a day to day basis? This would be more useful in a production environment (where an admin would want to see the logs for the entire day). I think that tail -f on most Linux machines will do the right thing. Most certainly on Solaris it will not. Either way we should set it to roll every day or disable rolling altogether. --jason - Original Message - From: David Budworth [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, December 29, 2001 11:20 AM Subject: [JBoss-dev] Why are we using RollingFileAppender in RH? I am curious, why we are using the RollingFileAppender in JBoss 3 alpha? With the amount of logging that happens by default, the log fills up very quickly, and the logfile gets rolled over. The problem is, since log4j actually renames the file, and creates a new one, any instance of tail server.log running, will still be watching the old inode (the backed up version). So you have to re-tail the file every few minutes. I understand using it for production purposes to save disk space, but in the Alpha version it seems kind of silly, and a pain to the developer trying to watch what's going on. Anyone mind if I switch it over? (just comment out the rolling stuff, so people who want it could put it back) I assume who ever made it this way was on windows, where the cygwin tail would have no problem watching the new file. But that doesn't work on *NIX machines. -David ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Why are we using RollingFileAppender in RH?
GA? I didn't say I was gonna do anything ;) You would rather is roll by size than by days? --jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Bill Burke Sent: Sunday, December 30, 2001 6:12 AM To: Jason Dillon; David Budworth; [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Why are we using RollingFileAppender in RH? I mind if you switch it over because we'll forget to switch it back after JBoss 3.0 goes GA. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jason Dillon Sent: Saturday, December 29, 2001 2:51 PM To: David Budworth; [EMAIL PROTECTED] Subject: Re: [JBoss-dev] Why are we using RollingFileAppender in RH? Can we set it to roll on a day to day basis? This would be more useful in a production environment (where an admin would want to see the logs for the entire day). I think that tail -f on most Linux machines will do the right thing. Most certainly on Solaris it will not. Either way we should set it to roll every day or disable rolling altogether. --jason - Original Message - From: David Budworth [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, December 29, 2001 11:20 AM Subject: [JBoss-dev] Why are we using RollingFileAppender in RH? I am curious, why we are using the RollingFileAppender in JBoss 3 alpha? With the amount of logging that happens by default, the log fills up very quickly, and the logfile gets rolled over. The problem is, since log4j actually renames the file, and creates a new one, any instance of tail server.log running, will still be watching the old inode (the backed up version). So you have to re-tail the file every few minutes. I understand using it for production purposes to save disk space, but in the Alpha version it seems kind of silly, and a pain to the developer trying to watch what's going on. Anyone mind if I switch it over? (just comment out the rolling stuff, so people who want it could put it back) I assume who ever made it this way was on windows, where the cygwin tail would have no problem watching the new file. But that doesn't work on *NIX machines. -David ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Why are we using RollingFileAppender in RH?
I am curious, why we are using the RollingFileAppender in JBoss 3 alpha? With the amount of logging that happens by default, the log fills up very quickly, and the logfile gets rolled over. The problem is, since log4j actually renames the file, and creates a new one, any instance of tail server.log running, will still be watching the old inode (the backed up version). So you have to re-tail the file every few minutes. I understand using it for production purposes to save disk space, but in the Alpha version it seems kind of silly, and a pain to the developer trying to watch what's going on. Anyone mind if I switch it over? (just comment out the rolling stuff, so people who want it could put it back) I assume who ever made it this way was on windows, where the cygwin tail would have no problem watching the new file. But that doesn't work on *NIX machines. -David ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Why are we using RollingFileAppender in RH?
I have been changing the log size to 10MB. If you don't have 10MB on your development machine, you have much bigger problems. -dain -Original Message- From: David Budworth [mailto:[EMAIL PROTECTED]] Sent: Saturday, December 29, 2001 1:21 PM To: [EMAIL PROTECTED] Subject: [JBoss-dev] Why are we using RollingFileAppender in RH? I am curious, why we are using the RollingFileAppender in JBoss 3 alpha? With the amount of logging that happens by default, the log fills up very quickly, and the logfile gets rolled over. The problem is, since log4j actually renames the file, and creates a new one, any instance of tail server.log running, will still be watching the old inode (the backed up version). So you have to re-tail the file every few minutes. I understand using it for production purposes to save disk space, but in the Alpha version it seems kind of silly, and a pain to the developer trying to watch what's going on. Anyone mind if I switch it over? (just comment out the rolling stuff, so people who want it could put it back) I assume who ever made it this way was on windows, where the cygwin tail would have no problem watching the new file. But that doesn't work on *NIX machines. -David ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Why are we using RollingFileAppender in RH?
Either crank up the default log size or fix the excessive logging by adjusting the priorities being used. - Original Message - From: David Budworth [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, December 29, 2001 11:20 AM Subject: [JBoss-dev] Why are we using RollingFileAppender in RH? I am curious, why we are using the RollingFileAppender in JBoss 3 alpha? With the amount of logging that happens by default, the log fills up very quickly, and the logfile gets rolled over. The problem is, since log4j actually renames the file, and creates a new one, any instance of tail server.log running, will still be watching the old inode (the backed up version). So you have to re-tail the file every few minutes. I understand using it for production purposes to save disk space, but in the Alpha version it seems kind of silly, and a pain to the developer trying to watch what's going on. Anyone mind if I switch it over? (just comment out the rolling stuff, so people who want it could put it back) I assume who ever made it this way was on windows, where the cygwin tail would have no problem watching the new file. But that doesn't work on *NIX machines. -David ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Why are we using RollingFileAppender in RH?
Can we set it to roll on a day to day basis? This would be more useful in a production environment (where an admin would want to see the logs for the entire day). I think that tail -f on most Linux machines will do the right thing. Most certainly on Solaris it will not. Either way we should set it to roll every day or disable rolling altogether. --jason - Original Message - From: David Budworth [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, December 29, 2001 11:20 AM Subject: [JBoss-dev] Why are we using RollingFileAppender in RH? I am curious, why we are using the RollingFileAppender in JBoss 3 alpha? With the amount of logging that happens by default, the log fills up very quickly, and the logfile gets rolled over. The problem is, since log4j actually renames the file, and creates a new one, any instance of tail server.log running, will still be watching the old inode (the backed up version). So you have to re-tail the file every few minutes. I understand using it for production purposes to save disk space, but in the Alpha version it seems kind of silly, and a pain to the developer trying to watch what's going on. Anyone mind if I switch it over? (just comment out the rolling stuff, so people who want it could put it back) I assume who ever made it this way was on windows, where the cygwin tail would have no problem watching the new file. But that doesn't work on *NIX machines. -David ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
