All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] tools/xc: restore logging in xc_save
Date: Mon, 4 Feb 2013 11:23:31 +0100	[thread overview]
Message-ID: <20130204102331.GA6328@aepfle.de> (raw)
In-Reply-To: <1359972720.5281.20.camel@zakaz.uk.xensource.com>

On Mon, Feb 04, Ian Campbell wrote:

> On Fri, 2013-02-01 at 18:58 +0000, Olaf Hering wrote:
> > +    lvl = si.flags & XCFLAGS_DEBUG ? XTL_DEBUG: XTL_DETAIL;
> > +    lflags = XTL_STDIOSTREAM_HIDE_PROGRESS;
> 
> Would it be useful (as an extension) to implement an XTL_STDIOSTREAM
> flag which makes it output something more suitable for logging,
> e.g. ...10%...20%...30%... 
> (or perhaps automatic based on isatty(outputfd)?)

I was thinking about that, to extend the called progress functions. In
the case of xend.log it would produce many lines of progress.
Since the default xend logging is limited to 1MB, the xend.log file
would be rotated quickly and maybe useful logging output will be lost?

But for other callers of the progress functions it might be useful to
have a parsable output so that they dont have to jump through the hoops.
No idea if any caller makes use of the progress, given that it did not
work at all without the other patch I sent last Friday.

> > +    l = (xentoollog_logger *)xtl_createlogger_stdiostream(stderr, lvl, lflags);
> 
> Might this fail and therefore require error handling?

If it fails then no logging will happen.

> The lvl and lflags variables seem a bit useless to me.

They are there to keep the lines short.

Olaf

  reply	other threads:[~2013-02-04 10:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 18:58 [PATCH] tools/xc: restore logging in xc_save Olaf Hering
2013-02-04 10:12 ` Ian Campbell
2013-02-04 10:23   ` Olaf Hering [this message]
2013-02-04 10:37     ` Ian Campbell
2013-02-04 10:50       ` Olaf Hering
2013-02-04 11:03         ` Ian Campbell
2013-02-13 13:47   ` Olaf Hering
2013-02-13 14:22     ` Olaf Hering

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=20130204102331.GA6328@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=Ian.Campbell@citrix.com \
    --cc=xen-devel@lists.xen.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 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.