dblog.txt needs a size Limit (5mb would be nice)

Hanako · Post by **Hanako** » Sat Apr 14, 2007 3:06 pm

I didn't find any threads addressing this issue so I decided to bring it up here. I just noticed an extremely fragmented 750MB dblog.txt file when doing some spring cleaning.

Would it be possible to limit this file size or disable logging when you don't need it?

Hoerie · Post by **Hoerie** » Sat Apr 14, 2007 6:23 pm

Yeah, I agree...mine is only 150mb but still, a huge waste of space if it is only used as a logfile.

Amour · Post by **Amour** » Sat Apr 14, 2007 10:59 pm

Thank you for pointing this out. I just deleted mine, now.

Post by **fahrenheit** » Sun Apr 15, 2007 1:28 pm

on ntfs file systems you can compress the files, you will save tons of space that way

suppy · Post by **suppy** » Sun Apr 15, 2007 7:33 pm

fahrenheit wrote:on ntfs file systems you can compress the files, you will save tons of space that way

oh lord, please tell me you did not just suggest this >_<

Post by **fahrenheit** » Sun Apr 15, 2007 9:45 pm

i did

i can give you another good one: ln -sv /dev/null dblog.txt

that would also solve your problem

Hoerie · Post by **Hoerie** » Sun Apr 15, 2007 11:37 pm

If the log is only there to take up space, then overwriting it instead of appending would be better, who wants 200 mb of logfile anyway?
Unless of course it is somehow important...

Hanako · Post by **Hanako** » Mon Apr 16, 2007 3:35 am

Logs do come in useful when troubleshooting and sometimes having a record of the last few executions helps in tracking down problems. Thats why I suggested some kind of size limit or an expiration on log dates.

NTFS compression can be useful on archiving and backup drives, but I prefer not to use it because of the performance hit. Its also not usually necessary when you have 3TB of storage space.