hi all
hoping someone can help here,is there any way to reduce the size of a console log ????
our server is trying to set up a stats log ,to register the number of player kills /deaths .
but we are getting log sizes of 4 gig and over !!!!
we have tried setting developer to 1 or 2 ,log-file to 1,2,or 3 but still the logs are huge .
is there a way ??? or will we just have to accept that's the way it is .Dax
Find out what is spamming your log.
This is what we used when we used to log stats.
set developer 2
seta g_logsync "1"
seta logfile 3
seta g_log "qconsole.log"
You also need to fix as many errors you can that were left in by the developers. Grab a log of a complete map rotation and fix any scripts that may be generating errors aswell. All of this adds to log girth.
hi all ....
sorry for the delay getting back ...pressures of work !!!!
thanks all for the feedback ...will help nicely.....Dax
hi again ...
just checking through the console log and on a player entering the server we are getting
"debug: player(1)is neither allied or axis - $player(1).dmteam = spectator" changing to =allied
when player joins as allied .
this repeats constantly while the player is connected and stops once he leaves ,is this fixable ?
or a necessary function on the server side.
we normally get up to 20 players average no wonder the logs are big, lol.Dax.
What mods do you have in your server...
hi again ...ok sorted the debug thing ,the map that was giving the debug thing,did not exec the dmprecache.....inserted the line ,no more debug thing....(lol good terminology)Dax.
hi all ...
we were still getting the debug thing spamming the server log on almost all of the
standard maps .
so decided to investigate further .
turns out it was the all weapons mod, in particular the final part of the statement :
else
println "DEBUG: $player[" local.i "] is neither allied nor axis - $player[" local.i "].dmteam = " local.player.dmteam
}
waitframe
}
end
is it ok to // out this part of the statement or will that cause other problems ????