[cod] Logging facility...
Andre Lorbach
alorbach at ro1.adiscon.com
Wed Jul 26 04:26:05 EDT 2006
Yes setting pb_sv_logsync to 0 does solve/workaround the problem for the
moment, but will also deaktivate circular logging of the Punkbuster
Server.
--
deltaray
> -----Original Message-----
> From: john at sherrit.net [mailto:john at sherrit.net]
> Sent: Wednesday, July 26, 2006 9:59 AM
> To: cod at icculus.org
> Subject: Re: [cod] Logging facility...
>
> Does changing the pb_sv_logsync function stop it from
> creating the server logs in the PB folder? This is very
> annoying as I used to have automated server stats but this
> requires my file to have the same name.
>
> Since 1.2 the logs start at 000001 and go upwards each
> restart which is no use to me if my server restarts several
> times in one day.
>
>
>
> > Hi all,
> >
> > it would be great to get some official statement about the logging
> > facility of CallofDuty2!
> > Since the patch 1.2, so the so called circular logging "bug" was
> > introduced. We all know that we can disable it by setting the
> > punkbuster pb_sv_logsync to 0. When the 1.3 patch came out nothing
> > changed, and the Windows Version went even worse. Many people are
> > complaining that the Windows Server is locking the logfile for read
> > access. Thats another issue and not really related to this
> list, just wanted to mention it.
> >
> > If it is not a bug, please tell us it isn't one, it is a
> feature. For
> > stats application writters it is a little bit difficult now
> to analyse
> > logfiles. Circular logs requires a total different way of logfile
> > analysis. A clear statement about this issue would be great.
> >
> > thank you!
> > deltaray
> >
> >
> >
> >
>
>
> ---
> To unsubscribe, send a blank email to cod-unsubscribe at icculus.org
>
>
>
>
More information about the Cod
mailing list