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
