Re: RE: Re: [Openh323gk-developer] RopenLogFile() review

[Zygmuntowicz M. <m.z...@on...>]

I would agree on this, plus:
*) adding timestamp (in form 20040219_163302) to the rotated
    logfile, preferably before the extension, so file associations
    are preserved,
*) adding the rotatelog status line command - it will be of great
    help if you just need to enable debug, do some test and store
    the results in a separate file.

The simplicity is the key. The main reason for logrotate in the gk
is Windows platform. Unices have many tools to perform log rotation,
so the feature is not necessary here.
So let's try to not go beyond simple log rotate in the gk.

Per Kreipke <pe...@ti...> wrote:
>All that said, how about:
>* \'-o\' on command line implies no rotation
>   + file name and path are set by arg
>   + no INI settings needed
>   + overrides \'-f\' option if also present
>
>* \'-f\' on command line implies log rotation
>   + path and base file name are set by arg
>   + default rotation is daily
>   + checks INI settings to define alternate rotation period
>
>My $0.02,
>
>Per