From: Zheng Li <dev@zheng.li>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Dave Scott <Dave.Scott@citrix.com>, Joe Jin <joe.jin@oracle.com>,
"Luis R. Rodriguez" <mcgrof@suse.com>,
Luonengjun <luonengjun@huawei.com>,
Fanhenglong <fanhenglong@huawei.com>,
"Liuqiming (John)" <john.liuqiming@huawei.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v3 9/9] oxenstored: reduce syslog call overhead (fix typo)
Date: Fri, 26 Sep 2014 17:29:52 +0100 [thread overview]
Message-ID: <54259480.3090108@zheng.li> (raw)
In-Reply-To: <21541.36072.303567.573538@mariner.uk.xensource.com>
On 26/09/2014 16:57, Ian Jackson wrote:
> Zheng Li writes ("Re: [PATCH v3 9/9] oxenstored: reduce syslog call overhead (fix typo)"):
>> Please see the 3rd format (:characters format) in the linked document below
>> http://www.gnu.org/software/libc/manual/html_node/TZ-Variable.html
>
> That's great for glibc-based guests. But what about the BSDs ?
This code does xenstored access logging in Dom0. Looking at the supported Dom0 distros page on the wiki, its seems that only NetBSD is the concern here?
> I looked at
> http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html#tag_08
> and it just says that the : syntax is `implementation defined'.
I guess most BSDs adopt the same semantics. I searched for NetBSD libc manual and found this (starting from "if the value does not begin with a colon ...")
http://netbsd.gw.com/cgi-bin/man-cgi?tzset+3
Cheers,
Zheng
next prev parent reply other threads:[~2014-09-26 16:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 17:34 Some oxenstored improvements (v3) Zheng Li
2014-09-25 17:34 ` [PATCH v3 1/9] oxenstored: add a poll-based select mechanism Zheng Li
2014-09-25 17:34 ` [PATCH v3 2/9] oxenstored: add facilities to raise the max open fds uplimit Zheng Li
2014-09-25 17:34 ` [PATCH v3 3/9] oxenstored: add a --use-select command line flag Zheng Li
2014-09-25 17:34 ` [PATCH v3 4/9] oxenstored: catch the error when a connection is already deleted Zheng Li
2014-09-25 17:34 ` [PATCH v3 5/9] oxenstored: use hash table to store socket connections Zheng Li
2014-09-25 17:34 ` [PATCH v3 6/9] oxenstored: enable domain connection indexing based on eventchn port Zheng Li
2014-09-25 17:35 ` [PATCH v3 7/9] oxenstored: only process domain connections that notify us by events Zheng Li
2014-09-25 17:35 ` [PATCH v3 8/9] oxenstored: add a safe net mechanism for existing ill-behaved clients Zheng Li
2014-09-25 17:35 ` [PATCH v3 9/9] oxenstored: reduce syslog call overhead Zheng Li
2014-09-25 21:00 ` [PATCH v3 9/9] oxenstored: reduce syslog call overhead (fix typo) Zheng Li
2014-09-26 15:16 ` Ian Jackson
2014-09-26 15:33 ` Zheng Li
2014-09-26 15:57 ` Ian Jackson
2014-09-26 16:29 ` Zheng Li [this message]
2014-09-26 16:37 ` Ian Jackson
2014-09-26 16:38 ` Zheng Li
2014-09-29 14:37 ` Some oxenstored improvements (v3) Konrad Rzeszutek Wilk
2014-09-29 20:55 ` Dave Scott
2014-09-30 10:21 ` Zheng Li
2014-10-07 13:24 ` Konrad Rzeszutek Wilk
2014-10-08 12:59 ` Dave Scott
2014-10-08 13:01 ` Konrad Rzeszutek Wilk
2014-10-08 13:42 ` Ian Campbell
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=54259480.3090108@zheng.li \
--to=dev@zheng.li \
--cc=Dave.Scott@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=fanhenglong@huawei.com \
--cc=joe.jin@oracle.com \
--cc=john.liuqiming@huawei.com \
--cc=luonengjun@huawei.com \
--cc=mcgrof@suse.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).