From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xensource.com,
"Ian Jackson" <ian.jackson@eu.citrix.com>,
"Vasiliy Tolstov" <v.tolstov@selfip.ru>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH 2/3] libxl: hotplug scripts: stdout >& stderr
Date: Tue, 18 Mar 2014 17:47:14 +0000 [thread overview]
Message-ID: <532886A2.6030902@citrix.com> (raw)
In-Reply-To: <1395164658.11824.57.camel@kazak.uk.xensource.com>
On 18/03/14 17:44, Ian Campbell wrote:
> On Tue, 2014-03-18 at 17:08 +0000, Ian Jackson wrote:
>> Plumb hotplug scripts' stdout to stderr. That way if they print
>> anything (which really they shouldn't), it won't get mixed up with
>> the application's stdout. (Eg, perhaps with an xl migration
>> stream...)
>>
>> Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
>> CC: Roger Pau Monné <roger.pau@citrix.com>
>> CC: Vasiliy Tolstov <v.tolstov@selfip.ru>
>> CC: Ian Campbell <Ian.Campbell@citrix.com>
>> ---
>> tools/libxl/libxl_device.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/tools/libxl/libxl_device.c b/tools/libxl/libxl_device.c
>> index ba7d100..90f76b7 100644
>> --- a/tools/libxl/libxl_device.c
>> +++ b/tools/libxl/libxl_device.c
>> @@ -1031,7 +1031,7 @@ static void device_hotplug(libxl__egc *egc, libxl__ao_device *aodev)
>>
>> if (!pid) {
>> /* child */
>> - libxl__exec(gc, -1, -1, -1, args[0], args, env);
>> + libxl__exec(gc, -1, 2, -1, args[0], args, env);
> Do you think we should also put the script's stderr to the application's
> stderr?
>
> Acked-by: Ian Campbell <ian.campbell@citrix.com>
>
> as it stands.
>
> Ian.
Absolutely - anything on any stderr really needs to get to logs and
probably also to a human.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-03-18 17:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 12:28 broken live migration in xen 4.3 (release) Vasiliy Tolstov
2014-03-17 12:58 ` Ian Campbell
2014-03-17 15:45 ` Ian Jackson
2014-03-17 22:06 ` Vasiliy Tolstov
2014-03-17 22:07 ` Vasiliy Tolstov
2014-03-17 23:09 ` Vasiliy Tolstov
2014-03-17 23:25 ` Vasiliy Tolstov
2014-03-18 9:36 ` Ian Campbell
2014-03-18 9:49 ` Roger Pau Monné
2014-03-18 9:54 ` Ian Campbell
2014-03-18 16:13 ` Ian Jackson
2014-03-18 16:15 ` Ian Campbell
2014-03-18 17:08 ` [PATCH 1/3] libxl: Make libxl_exec tolerate foofd<=2 Ian Jackson
2014-03-18 17:08 ` [PATCH 2/3] libxl: hotplug scripts: stdout >& stderr Ian Jackson
2014-03-18 17:44 ` Ian Campbell
2014-03-18 17:47 ` Andrew Cooper [this message]
2014-03-18 18:12 ` Ian Jackson
2014-03-19 9:55 ` Ian Campbell
2014-03-19 13:41 ` Ian Jackson
2014-03-19 14:00 ` Vasiliy Tolstov
2014-03-18 17:08 ` [PATCH 3/3] libxl: hotplug scripts: stdin < /dev/null Ian Jackson
2014-03-18 17:46 ` Ian Campbell
2014-03-18 18:12 ` Ian Jackson
2014-03-18 17:43 ` [PATCH 1/3] libxl: Make libxl_exec tolerate foofd<=2 Ian Campbell
2014-03-18 18:14 ` Ian Jackson
2014-03-19 9:56 ` Ian Campbell
2014-03-18 9:53 ` broken live migration in xen 4.3 (release) Vasiliy Tolstov
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=532886A2.6030902@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=roger.pau@citrix.com \
--cc=v.tolstov@selfip.ru \
--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.