Re: [Xen-devel] c/s 17731 portability issues

To:	Christoph Egger <Christoph.Egger@xxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	Re: [Xen-devel] c/s 17731 portability issues
From:	Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date:	Mon, 26 May 2008 09:14:21 +0100
Cc:	Xiaowei Hu <xiaowei.hu@xxxxxxxxxx>, john.levon@xxxxxxx
Delivery-date:	Mon, 26 May 2008 01:14:25 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<200805261007.00725.Christoph.Egger@xxxxxxx>
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	Aci/CIAbvndN6yr7Ed2kDQAWy6hiGQ==
Thread-topic:	[Xen-devel] c/s 17731 portability issues
User-agent:	Microsoft-Entourage/11.4.0.080122

On 26/5/08 09:07, "Christoph Egger" <Christoph.Egger@xxxxxxx> wrote:

> Hi!
> 
> Changeset 17731 has some portability issues:
> 
> BSD ps has no --no-headers  argument.
> Solaris ps  has no --no-headers argument and -o has a different
> semantic.
> 
> For BSD it would be enough to just remove --no-headers.

Then the surrounding logic would need to be fixed up too. I wonder whether
it is even possible to extract process state from ps in an OS-neutral way?
The changeset isn't important or useful enough to keep if it's going to
cause portability problems.

 -- Keir

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

WARNING - OLD ARCHIVES

xen-devel

Re: [Xen-devel] c/s 17731 portability issues