From: Juergen Gross <jgross@suse.com>
To: Wei Liu <wei.liu2@citrix.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
David Vrabel <david.vrabel@citrix.com>
Subject: Re: XSA-180 follow-up: repurpose xenconsoled for logging
Date: Tue, 21 Jun 2016 17:10:18 +0200 [thread overview]
Message-ID: <576958DA.4000300@suse.com> (raw)
In-Reply-To: <20160621144607.GU1790@citrix.com>
On 21/06/16 16:46, Wei Liu wrote:
> Here is what we have gathered so far:
>
> 1. Virtlogd is not the right answer to XSA-180 because it is inherently
> designed to work within libvirt.
> 2. Syslog is not suitable because it doesn't provide a fd for QEMU to
> write to.
> 3. Logrotate is not suitable because it only rotates periodically.
Huh? Excerpt from `man logrotate`:
Each log file may be handled daily, weekly, monthly, or when it grows
too large.
So why is logrotate not suitable?
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-21 15:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 14:00 XSA-180 follow-up: repurpose xenconsoled for logging Wei Liu
2016-06-03 10:57 ` George Dunlap
2016-06-03 13:30 ` Wei Liu
2016-06-03 14:10 ` George Dunlap
2016-06-03 14:21 ` Wei Liu
2016-06-03 16:57 ` Ian Jackson
2016-06-06 15:56 ` Wei Liu
2016-06-03 17:38 ` Andrew Cooper
2016-06-06 10:12 ` George Dunlap
2016-06-06 13:03 ` Andrew Cooper
2016-06-06 15:48 ` Wei Liu
2016-06-07 9:57 ` George Dunlap
2016-06-07 10:18 ` Wei Liu
2016-06-06 20:47 ` Doug Goldstein
2016-06-07 11:43 ` Wei Liu
2016-06-21 14:46 ` Wei Liu
2016-06-21 15:10 ` Juergen Gross [this message]
2016-06-21 15:23 ` Ian Jackson
2016-06-21 15:11 ` Ian Jackson
2016-06-21 15:53 ` George Dunlap
2016-06-21 16:04 ` Ian Jackson
2016-06-21 16:17 ` George Dunlap
2016-06-22 0:58 ` Jim Fehlig
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=576958DA.4000300@suse.com \
--to=jgross@suse.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).