Jeff Squyres wrote:
> I notice that
>
> shell$ hwloc-bind
>
> (i.e., invoking hwloc-bind with no arguments)
>
> returns an exit status of 0. Shouldn't it return non-zero? I'd think it was
> an error if you didn't give hwloc-bind anything to do. For example, we
> wouldn't want a script with
On Thu, 2009-12-03 at 20:32 -0500, Jeff Squyres wrote:
> > > Ah, ok. To be clear, is it accurate to say that it is one of the
> > > following forms:
> > >
> > > - a hex number (without leading "0x" -- would "0x" be ignored if it is
> > > supplied?)
> >
> > We never used 0x there.
>
> Ok.
>
>
Jeff Squyres wrote:
> It might be good to safely ignore 0x if it's present, but that's a small
> feature enhancement that can be done at any time (I filed a future ticket).
>
It seems to work actually :)
>> We might want to drop the Linux "cpuset" word and use "cgroup" instead.
>> Both are
I installed the debian package of hwloc yesterday and discovered that
the default action of lstopo is to display a window with a picture in.
I guess I don't have the right development packages installed for this
to be enabled in my local build.
In my tool I want to ensure the text version is
Ashley Pittman wrote:
> I installed the debian package of hwloc yesterday and discovered that
> the default action of lstopo is to display a window with a picture in.
> I guess I don't have the right development packages installed for this
> to be enabled in my local build.
>
> In my tool I want
Ashley Pittman, le Fri 04 Dec 2009 11:06:12 +, a écrit :
> The debian version of -.txt (lstopo 0.9.3rc1) leaves my terminal with
> the colours inverted after I call it, I have to do a reset to get back
> to black on grey background.
Uh, odd. Which terminal are you using?
Samuel
On Fri, 2009-12-04 at 13:04 +0100, Samuel Thibault wrote:
> Ashley Pittman, le Fri 04 Dec 2009 11:06:12 +, a écrit :
> > The debian version of -.txt (lstopo 0.9.3rc1) leaves my terminal with
> > the colours inverted after I call it, I have to do a reset to get back
> > to black on grey
On Dec 4, 2009, at 1:09 AM, Brice Goglin wrote:
> > shell$ hwloc-bind
> >
> > (i.e., invoking hwloc-bind with no arguments)
> >
> > returns an exit status of 0. Shouldn't it return non-zero?
>
> Yeah maybe
I'm going to interpret that as "Hell yes! Please implement. THANKS!!!"
;-)
--
Jeff
On Dec 4, 2009, at 5:32 AM, Ashley Pittman wrote:
> > It might be good to safely ignore 0x if it's present, but that's a small
> > feature enhancement that can be done at any time (I filed a future ticket).
>
> Maybe not relevant but it bit me so I'll say it here, using "%x" with
> sscanf on a
On Dec 4, 2009, at 5:36 AM, Brice Goglin wrote:
> > It might be good to safely ignore 0x if it's present, but that's a small
> > feature enhancement that can be done at any time (I filed a future ticket).
>
> It seems to work actually :)
Hmm -- I don't think so...? "0x1" can't pass this test
10 matches
Mail list logo
