Tark
15th October, 2002, 08:19 AM
Hi,
It used to be I could watch (or scan a log file) for various people logging in to my server. Further, it seemed that logging was quiescent unless someone was logging in, maps were changing, etc. This was useful information for a variety of reasons.
With UT2K3, I don't see the same sort of info logged... for instance, no apparent logging of connections. Also, there is a constant (albeit slow) dribble of GameSpy heartbeat messages, SOCKET_ERRORs, etc that appear to be about useless for anything other than filling a log file.
Are there some options I can set anywhere that help to tailor logging output? Is connection attempt information still available?
Thanks!
Tark
It used to be I could watch (or scan a log file) for various people logging in to my server. Further, it seemed that logging was quiescent unless someone was logging in, maps were changing, etc. This was useful information for a variety of reasons.
With UT2K3, I don't see the same sort of info logged... for instance, no apparent logging of connections. Also, there is a constant (albeit slow) dribble of GameSpy heartbeat messages, SOCKET_ERRORs, etc that appear to be about useless for anything other than filling a log file.
Are there some options I can set anywhere that help to tailor logging output? Is connection attempt information still available?
Thanks!
Tark