Setting it to read only isn't helping with the spikes, unfortunately.
I'm not sure what exactly the debug code is doing that they left on, but
the logs aren't being flushed to file immediately after a snapshot
overflow so this stuff is building up in memory for a while.
Fletcher also talked about network packing code being rerun after a
drop, and I'm assuming this is the point that I am seeing spikes on my
servers. Steamauth drops have increased quite a bit in recent updates
and these seem to coincide with spikes I'm seeing.
On 7/11/2012 6:36 PM, brendan halley wrote:
If it's such a problem just run a cron that clears or deletes it. Have you
tried setting the file as read only?
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux