Dinesh Premalal 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).
So it is only two levels. Is that good enough?
The other concern is that, the code is already commited and it was never
discussed on this list, despite it being a major decision :)
Have we implemented this so that it works for all the deployment models
like simple http/tcp servers as well as the httpd module?
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.
I guess you looked on your PC, it is not a production system, it is? ;-)
On my PC, apache error log is 491K already and I hardly run it on a
daily basis.
Samisa...
Dinesh
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Samisa Abeysinghe
Software Architect; WSO2 Inc.; http://www.wso2.com/
email: [EMAIL PROTECTED]; cell: +94 77 753 7913
"Oxygenating the Web Service Platform."
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
