|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
My two cents on why DSpace rotates it's own logs -- mostly it's just good "default" practice (as it's one less thing to have to think about during installation). Plus, "logrotate" is a Linux tool....whereas DSpace is built to run on any OS.
Also, since DSpace uses log4j, you can choose to change your 'log4j.properties' file to no longer do log rotation, as you desire. Log4J supports a variety of "appenders" that you can choose from, including:
* org.apache.log4j.FileAppender (just appends to a log file..no rotation)
* org.apache.log4j.ConsoleAppender (writes logs to stdout)
So, hypothetically (I haven't tried this, so test it first), you could use 'logrotate', and just change the default DSpace log4j.properties so that all of the A1-A3 "appenders" are:
log4j.appender.A1=org.apache.log4j.FileAppender