Server logfile options?

[Featherbane]

I am an admin for a small server, we're trying out Unleashed 1.1.3, we (I) decided to have biomes o plenty enabled, and after a week of no one being logged on, I happened to take a looksee at the logs, to see what if anything occurred while we were all off doing other things, and there was a nice 100meg log. It had almost entirely been filled with:

 . . . . [FINE] [ForgeModLoader] Saved ModFlags NBT data file successfully.

After some checking, I found it MIGHT have been BoP, so disabled it, recreated the world and that message went away. Not happy with losing some really pretty biomes, I tested it on its own, and no NBT spam. I have since moved further testing to a local server (so my friends stop exploding that I keep recreating the world : )

On the local server, just the act of signing into the world, and signing off (no building, aside from what gets generated around player) begins the spam.

I HAVE found out, that this message isn't a terrible thing, and we could ignore it - only, a week of no one on the server, and the log file ballooned to 100megs. I have considered log-rotation to keep it under control, or sending the entire thing into null, but neither option is satisfactory, so Is there any possible way to suppress that message from the logfile?

NOTE: in Ultimate, our logs on a busy week without any such message would get large, I am slightly worried that with this NBT message, it would get excessively large.

 

[pherce]

Be thankful you never ran a Tekkit 1.2.5 server, damn. Slotchanging and all sorts of constant spam...

Anyway, you can try http://dev.bukkit.org/bukkit-plugins/thislogmustdie/, however, some mods may not call the same logger that the plugin monitors so the spam could get through the filter (we ended up creating our own). If you are rotating logs daily then you can always make a quick script to clean the logs after they've been rotated out.