Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@trafficserver.apache.org
MIME-Version: 1.0
References: 
 <CALKvBna388A9rW93CYO8cgZds1QDoiD1ZuBVnWRJy9f0Y8wGQg@mail.gmail.com>
 <46C033BF-950C-4DB4-AB7E-1DE43AA4D504@apache.org>
In-Reply-To: <46C033BF-950C-4DB4-AB7E-1DE43AA4D504@apache.org>
From: "Adam W. Dace" <colonelforbin74@gmail.com>
Date: Tue, 30 Jun 2015 22:56:43 +0000
Message-ID: 
 <CALKvBnbsuvK4iTNaOZW6ED0Ny3Piy-W5xL8ZgZzCbAA85dTa0g@mail.gmail.com>
Subject: Re: ATS 6.0 Logging Question
To: users@trafficserver.apache.org
Content-Type: multipart/alternative; boundary=90e6ba3fcc7945c1470519c41fda

--90e6ba3fcc7945c1470519c41fda
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I'll bet it does and I just have it configured incorrectly.

I only have one LogObject defined in logs_xml.config.

If anyone knows how to properly define the error log, please let me know.
 :)


On Tue, Jun 30, 2015 at 4:46 PM Leif Hedstrom <zwoop@apache.org> wrote:

>
> > On Jun 30, 2015, at 5:53 AM, Adam W. Dace <colonelforbin74@gmail.com>
> wrote:
> >
> > First, let me say the new logging regime is looking good.  Really good.
> I've had quite the fun time defining my own logging format and it seems t=
o
> be working quite well.
> >
> > The only thing I miss at all about the old logging system was the idea
> that errors get logged into a different file.
> >
> > Is there any way to do this in the new regime?  I'm guessing not but I
> wanted to just ask.
>
>
> That should still be the case. Does it not do that? If so, we have a
> serious problem. The =E2=80=9Cnew regime=E2=80=9D is not that new, we sim=
ply removed the
> hardcoded formats (and related records.config settings), and moved them a=
ll
> to the XML config file. The error log should not have changed.
>
> =E2=80=94 Leif
>
>

--90e6ba3fcc7945c1470519c41fda
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I&#39;ll bet it does and I just have it configured incorre=
ctly.<br><br>I only have one LogObject defined in logs_xml.config.<div><br>=
</div><div>If anyone knows how to properly define the error log, please let=
 me know. =C2=A0:)</div><div><div><br></div></div></div><br><div class=3D"g=
mail_quote"><div dir=3D"ltr">On Tue, Jun 30, 2015 at 4:46 PM Leif Hedstrom =
&lt;<a href=3D"mailto:zwoop@apache.org">zwoop@apache.org</a>&gt; wrote:<br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><br>
&gt; On Jun 30, 2015, at 5:53 AM, Adam W. Dace &lt;<a href=3D"mailto:colone=
lforbin74@gmail.com" target=3D"_blank">colonelforbin74@gmail.com</a>&gt; wr=
ote:<br>
&gt;<br>
&gt; First, let me say the new logging regime is looking good.=C2=A0 Really=
 good.=C2=A0 I&#39;ve had quite the fun time defining my own logging format=
 and it seems to be working quite well.<br>
&gt;<br>
&gt; The only thing I miss at all about the old logging system was the idea=
 that errors get logged into a different file.<br>
&gt;<br>
&gt; Is there any way to do this in the new regime?=C2=A0 I&#39;m guessing =
not but I wanted to just ask.<br>
<br>
<br>
That should still be the case. Does it not do that? If so, we have a seriou=
s problem. The =E2=80=9Cnew regime=E2=80=9D is not that new, we simply remo=
ved the hardcoded formats (and related records.config settings), and moved =
them all to the XML config file. The error log should not have changed.<br>
<br>
=E2=80=94 Leif<br>
<br>
</blockquote></div>

--90e6ba3fcc7945c1470519c41fda--