Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Received-SPF: pass (athena.apache.org: domain of rajikacc@gmail.com designates
 64.233.166.178 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=fo2Vk11MKdrKztLFwcGl7BxuY2IN8rIVbg6nlITNzD0YqFbKRGuxUDJIy4Zjc9sLOOOEkzKZcpmk9DMg6N7QRgHWnoS+r5m0kARQ6Df1rBoIPrSWY0Fvck9Qa70Jd3zt3Luana4Z1wSWigd0/bGv+qPGMc/MGuRBtwYgMiJRo0k=
Message-ID: <696bc1d50711030529s2e4cccb3ke2cacb3b8dfc1d5c@mail.gmail.com>
Date: Sat, 3 Nov 2007 17:59:05 +0530
From: "Rajika Kumarasiri" <rajikacc@gmail.com>
To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Subject: Re: maximum log file size 1M
In-Reply-To: <87d4urjzjz.fsf@etch.wso2.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_13290_30112301.1194092945693"
References: <472C111B.3060306@gmail.com> <87d4urjzjz.fsf@etch.wso2.com>

------=_Part_13290_30112301.1194092945693
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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


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 <xydinesh@gmail.com> wrote:
>
> Hi,
>
> Samisa Abeysinghe <samisa.abeysinghe@gmail.com> 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.
>
> Dinesh
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>
>


-- 
comp.lang.c - http://groups.google.com/group/comp.lang.c/topics

------=_Part_13290_30112301.1194092945693
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

hello,<br>The most common way of handling log file growth is via a rotation procedure.
<br><br>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 &#39;.1&#39;
suffix, rename the old &#39;.1&#39; file to have a &#39;.2&#39; suffix, and so on. The last
copy of the log file (with suffix &#39;.n&#39;) should be erased. The renaming process is done from last to first, otherwise we will end up with &#39;n&#39;
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.<br><br>Rajika<br><br><div><span class="gmail_quote">On 11/3/07, <b class="gmail_sendername">Dinesh Premalal</b> &lt;<a href="mailto:xydinesh@gmail.com">xydinesh@gmail.com
</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br><br>Samisa Abeysinghe &lt;<a href="mailto:samisa.abeysinghe@gmail.com">
samisa.abeysinghe@gmail.com</a>&gt; writes:<br><br>&gt; I saw this commit where the maximum log file size is set to 1M.<br>&gt;<br>&gt; I am just curious to know, what happens when it exceeds 1M?<br>AFAIK, that file is backed up (
axis2.log.1) and start new file<br>(axis2.log). Then , if new one also exceeds 1M, it is backed up over<br>writing old backed up file.<br><br>Finally, system has only two files, current log file (axis2.log) and immediate<br>
recent log file (axis2.log.1).<br><br>&gt;<br>&gt; Also, for a production system, I deem that 1M is too small.<br>I guess not :), I looked at some other logs (#ls -lah<br>/var/log/ ) they even hardly exceeds 300K.<br><br>
Dinesh<br><br><br>---------------------------------------------------------------------<br>To unsubscribe, e-mail: <a href="mailto:axis-c-dev-unsubscribe@ws.apache.org">axis-c-dev-unsubscribe@ws.apache.org</a><br>For additional commands, e-mail: 
<a href="mailto:axis-c-dev-help@ws.apache.org">axis-c-dev-help@ws.apache.org</a><br><br></blockquote></div><br><br clear="all"><br>-- <br>comp.lang.c - <a href="http://groups.google.com/group/comp.lang.c/topics">http://groups.google.com/group/comp.lang.c/topics
</a>

------=_Part_13290_30112301.1194092945693--