[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [OSSTEST PATCH 24/24] Serial::xenuse: Send xenuse output to /dev/null
Like sympathy, attaching via xenuse causes xenuse to send output from the host to its own stdout. But we don't want the ts-logs-capture stdout to contain this serial output, interleaved with its own log messages. We'll capture the whole serial log from the xenuse logfile. So redirect it to /dev/null. I have checked that xenuse does (at least sometimes, eg when given a nonexistent hostname) use stderr when something actually goes wrong. Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> Tested-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> --- v17: New patch --- Osstest/Serial/xenuse.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Osstest/Serial/xenuse.pm b/Osstest/Serial/xenuse.pm index e1270e0..c79d986 100644 --- a/Osstest/Serial/xenuse.pm +++ b/Osstest/Serial/xenuse.pm @@ -54,7 +54,7 @@ sub keys_prepare { my $xenuse= $c{XenUsePath} || "xenuse"; - open XENUSEWRITE, "|$xenuse -t $ho->{Name}" or die $!; + open XENUSEWRITE, "|$xenuse -t $ho->{Name} >/dev/null" or die $!; autoflush XENUSEWRITE 1; $mo->keys_write('force attach', "\x05cf", 1); # ^E c f == force attach -- 1.7.10.4 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |