All,
I'm curious about how people are managing their log files. In
particular, I've noticed that dspace.log.* and cocoon.log.* are around
200MB apiece, per day. We zip them at night, but even so, they're
taking a ridiculous amount of storage space on our VPS. What are people
doing with
Hi Alan,
take a look at logrotate. It's a standard unix tool to manage your
logs, including splitting logs by day (DSpace does this itself),
keeping the last N days around and compressing and/or moving the rest
elsewhere. It's very configurable.
Regards,
~~helix84
Also, if some logs are too detailed for you which makes them grow too
large, you can raise loglevel, e.g. from INFO to WARN. Although I
personally wouldn't do it.
https://wiki.duraspace.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-TurningonDebugging(optional)
Regards,
~~helix84
Hey, helix.
I zip my logs nightly with something like this:
find /home/dspace/log/ ! -iname *.gz -iname dspace.log.* -o ! -iname
*.gz -iname cocoon.log.* -daystart -mtime +1 -exec ionice -c2 -n7
gzip {} \;
I'm more wondering what people use these logs for, and how/if they
archive them
Al 19/04/12 09:53, En/na Alan Orth ha escrit:
All,
I'm curious about how people are managing their log files. In
particular, I've noticed that dspace.log.* and cocoon.log.* are around
200MB apiece, per day. We zip them at night, but even so, they're
taking a ridiculous amount of storage
As i know , the log files are not needed if you've generated your stat
reports, you just keep that generated ones into archival, the log files are
just the source for the task, not the outcomes.
2012/4/19 Alexandre Magaz Graça alexandre.ma...@udl.cat
Al 19/04/12 09:53, En/na Alan Orth ha
6 matches
Mail list logo
