From: Gihan Munasinghe <GMunasinghe@flexiant.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: syslog support to xentoollog
Date: Thu, 03 Jun 2010 15:31:56 +0100 [thread overview]
Message-ID: <4C07BCDC.8020808@flexiant.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1006031121020.3401@kaball-desktop>
Stefano Stabellini wrote:
> On Wed, 2 Jun 2010, Gihan Munasinghe wrote:
>
>> Guys
>>
>> Is there any plans to add syslog support in to xentoollog.
>>
>> Is this something that xentoollog would like to adopt .
>>
>>
>
> That is something we definitely want, patches are welcome :-)
>
>
Great I'll do some patching to get syslog working.
looking at the xentool.h, following definitions
#define XTL_STDIOSTREAM_SHOW_PID 01u
#define XTL_STDIOSTREAM_SHOW_DATE 02u
#define XTL_STDIOSTREAM_HIDE_PROGRESS 04u
I would suggest to be as
#define XTL_SHOW_PID 01u
#define XTL_SHOW_DATE 02u
#define XTL_HIDE_PROGRESS 04u
So it will be more generic for any loggers that will be implemented
also is everyone happy with following loglevel mappings between
xentoollog_level and syslog
{XTL_DEBUG,LOG_DEBUG},
{XTL_VERBOSE,LOG_DEBUG},
{XTL_DETAIL,LOG_DEBUG},
{XTL_PROGRESS,LOG_DEBUG},
{XTL_INFO,LOG_INFO},
{XTL_NOTICE,LOG_NOTICE},
{XTL_WARN,LOG_WARNING},
{XTL_ERROR,LOG_ERR},
{XTL_CRITICAL,LOG_CRIT}
Thanks
Gihan
next prev parent reply other threads:[~2010-06-03 14:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 21:39 syslog support to xentoollog Gihan Munasinghe
2010-06-03 10:21 ` Stefano Stabellini
2010-06-03 14:31 ` Gihan Munasinghe [this message]
2010-06-04 11:25 ` Ian Jackson
2010-06-05 0:51 ` [PATCH] " Gihan Munasinghe
2010-06-07 6:51 ` Keir Fraser
2010-06-07 10:37 ` Ian Jackson
2010-06-07 10:33 ` Ian Jackson
2010-06-07 11:36 ` Gihan Munasinghe
2010-06-07 11:51 ` Ian Jackson
2010-06-07 10:36 ` Ian Jackson
2010-06-07 11:37 ` Gihan Munasinghe
2010-06-07 11:51 ` Ian Jackson
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=4C07BCDC.8020808@flexiant.com \
--to=gmunasinghe@flexiant.com \
--cc=stefano.stabellini@eu.citrix.com \
--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.