Depends what you want to do with the log files. Do you analyse them in any way? -Make sure you are only logging what you are interested in; log4j allows for different log levels for different packages. You could reduce the general log level to error and increase it to info for the packages/classes you want to know more about. -Consider deleting old log files.
Anja On 03/02/2014 10:03, ad...@unhas.ac.id wrote: > Dear All, > > Current size of our dspace is like this: > /log: 90 Gb > /assetstore: 12 Gb > /SOLR: 5.4 Gb > > Can you give suggestions on how to 'cut' the size of log directory? > any hints for future daily operational to minimize the log? > > Best Regards, > Ady W. Paundu > > ---- > Powered by PTIK UNHAS ~ http://unhas.ac.id/ > > > ------------------------------------------------------------------------------ > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk > _______________________________________________ > DSpace-tech mailing list > DSpace-tech@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-tech > List Etiquette: > https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette > > ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
