From: Aron Griffis <aron@hp.com>
To: Jeremy Katz <katzj@redhat.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Move logs under /var/log/xen
Date: Mon, 28 Aug 2006 11:49:26 -0400 [thread overview]
Message-ID: <20060828154925.GD3476@fc.hp.com> (raw)
In-Reply-To: <1155935231.11663.56.camel@aglarond.local>
Jeremy Katz wrote: [Fri Aug 18 2006, 05:07:11PM EDT]
> On Fri, 2006-08-18 at 21:50 +0100, Ian Pratt wrote:
> > > The attached patch moves all of the various log files created by xen to
> > > be under /var/log/xen instead of under /var/log directly. This has the
> > > advantage of cleaning things up a little[1] and also can make it easier
> > > to restrict the permissions needed by xend.
> >
> > Alternatively, should we just be sending all of these messages to syslog and then
> > syslog.conf figure out what to do with them? I've often thought it would be handy
> > to have all the messages in one place, and with time stamps.
>
> I think right now, things are a bit verbose to just be doing everything
> via syslog -- it'd be kind of like sending all of your apache logs to
> syslog. Things would just get overrun to the point of being less
> useful.
>
> Having the logs split out is actually kind of nice from my point of view
> -- I just want them a little bit more so :-)
I like the idea of consolidating the logs to /var/log/xen, however
I don't quite understand how the logs could be too verbose for syslog.
With syslog configuration, you can branch them out to separate files
anyway, to keep the status quo. The advantage of using syslog is that
you can also do interesting things like filtering and sending over the
network to a central logging machine.
Aron
next prev parent reply other threads:[~2006-08-28 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 20:50 [PATCH] Move logs under /var/log/xen Ian Pratt
2006-08-18 21:07 ` Jeremy Katz
2006-08-28 15:49 ` Aron Griffis [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-28 16:35 Ian Pratt
2006-08-18 18:33 Jeremy Katz
2006-08-25 14:26 ` Jeremy Katz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060828154925.GD3476@fc.hp.com \
--to=aron@hp.com \
--cc=katzj@redhat.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.