Hi all,

> hello,
> The most common way of handling log file growth is via a rotation
> procedure.

I don't think we have a serious log file size problem to go for a rotation
process.

>
>
> First we define how many old copies of the log file we want to
> create/keep,

> and the rate at which they should be rotate(once a day, once a week and so
> on). When we rotate a given log file, the original file should rename to
> have a '.1' suffix, rename the old '.1' file to have a '.2' suffix, and so
> on. The last copy of the log file (with suffix '.n') should be erased. The
> renaming process is done from last to first, otherwise we will end up with
> 'n' copies of the current log file. Once done, we create a new, empty log
> file, with the same access permissions as the original log file.
>
> Rajika
>
> On 11/3/07, Dinesh Premalal <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>>
>> Samisa Abeysinghe <[EMAIL PROTECTED]> writes:
>>
>> > I saw this commit where the maximum log file size is set to 1M.
>> >
>> > I am just curious to know, what happens when it exceeds 1M?
>> AFAIK, that file is backed up (axis2.log.1) and start new file
>> (axis2.log). Then , if new one also exceeds 1M, it is backed up over
>> writing old backed up file.
>>
>> Finally, system has only two files, current log file (axis2.log) and
>> immediate
>> recent log file (axis2.log.1).
>>
>> >
>> > Also, for a production system, I deem that 1M is too small.
>> I guess not :), I looked at some other logs (#ls -lah
>> /var/log/ ) they even hardly exceeds 300K.

You can always specify the MAX_SIZE of the log file.
(https://issues.apache.org/jira/browse/AXIS2C-732).

But, 1MB would not be enough is my personal belief. I was trying to figure
out some memory leaks, and, frequently started and stopped the simple axis
server. My log file exceeded 1MB in 52 runs. Therefore, I believe that it
should be at least 5MB+ (making it some 250+ runs).

Senaka.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to