Blockland Forums > General Discussion
Kaphost Blockland Servers
Jasa1:
--- Quote from: Kalphiter on January 20, 2012, 12:04:43 PM ---Ok, everyone now has the new copy of logwriter which now makes new files after the log is 1024KB. It's already activated in every server.
--- End quote ---
Does this apply to the console.log?
Kalphiter:
--- Quote from: Jasa1 on January 20, 2012, 04:00:43 PM ---Does this apply to the console.log?
--- End quote ---
--- Quote from: Kalphiter on January 20, 2012, 12:04:43 PM ---logwriter
--- End quote ---
I do wish that, however, it's my next step for java to lock the console log and write it itself.
DontCare4Free:
--- Quote from: Kalphiter on January 20, 2012, 04:04:31 PM ---I do wish that, however, it's my next step for java to lock the console log and write it itself.
--- End quote ---
Or you could just get a write-only mutex.
Kalphiter:
--- Quote from: DontCare4Free on January 20, 2012, 04:35:20 PM ---Or you could just get a write-only mutex.
--- End quote ---
Why?
It'll need to split up the log into 1MB chunks (or more, whatever I choose), and since it will do that there is no point in keeping console.log.
Boomerangdog:
My server just crashed, at exactly 9:32AM, EST.
Same thing happened too. The data corrupted, and it crashed when it was seeding ores and trees for DRPG. Every other time it crashed when not seeding.