Ralph,
To be honest any joker can probably have a "/proc" under any
non-Linux OS - there is noting sacred about the name. So, would in not
make the most sense (both simple and robust) to just check $target_os
and build exclusively for Linux?
-Paul
On 3/24/2011 7:01 PM, Ralph Castain wrot
replies below...
On 3/24/2011 7:00 PM, Silas Silva wrote:
I'm actually not building it from scratch:-) I'm using the pkgsrc
package manager (www.pkgsrc.org) that is source based and create binary
packages in the local computer. The problem is that the contents of the
package differs in the ca
On Thu, Mar 24, 2011 at 08:03:25PM -0600, Ralph Castain wrote:
> Why would you want to do that, if it even were possible (which I'm
> pretty sure it isn't)?
I'm not a GNU/Linux user, so I don't know whether or not /proc is always
mounted... This was just a doubt.
--
Silas Silva
On Mar 24, 2011, at 8:00 PM, Silas Silva wrote:
> Hi Paul,
>
> On Thu, Mar 24, 2011 at 06:52:23PM -0700, Paul H. Hargrove wrote:
>> Silas,
>>
>> FYI: openmpi-1.4.1 is in the package repo for NetBSD 5.1. So, you
>> might not need to build from scratch at all, depending on your
>> desired use.
>
Thanks Paul - very illuminating!
Looks to me like I'm okay for OpenBSD as I won't find /proc and so won't build
the Linux module.
I have a problem with FreeBSD because /proc exists, but I won't find what I'm
looking for, so I'll have to add a test for that case and not-build when
FreeBSD is de
... and AIX 6.1 also has a /proc but no cpuinfo or meminfo
On 3/24/2011 6:52 PM, Paul H. Hargrove wrote:
To "prefetch" the next logical question:
On a FreeBSD 8.1 system I find that /proc exists but does not contain
cpuinfo or meminfo
On a OpenBSD 4.8 system I find that there is no /proc
--
Hi Paul,
On Thu, Mar 24, 2011 at 06:52:23PM -0700, Paul H. Hargrove wrote:
> Silas,
>
> FYI: openmpi-1.4.1 is in the package repo for NetBSD 5.1. So, you
> might not need to build from scratch at all, depending on your
> desired use.
I'm actually not building it from scratch :-) I'm using the
Silas,
FYI: openmpi-1.4.1 is in the package repo for NetBSD 5.1. So, you might
not need to build from scratch at all, depending on your desired use.
Jeff,
When available (remember that unlike Linux /proc might not be mounted by
default) the /proc/cpuinfo and /proc/meminfo on NetBSD 5.1 are
Is the data the same in /proc between NetBSD and Linux?
We're currently looking in /proc/cpuinfo and /proc/meminfo for some specific
key / data pairs.
On Mar 24, 2011, at 2:29 PM, Silas Silva wrote:
> Hello there,
>
> I'm using OpenMPI for educational reasons. It works pretty fine under
> G
On Mar 24, 2011, at 3:57 PM, Hugo Meyer wrote:
> 2011/3/24 Ralph Castain
> You really don't want to do it that way - you'll create a major confusion in
> mpirun and the other daemons about who is where. Have you looked at the code
> in orte/mca/errmgr/hnp/errmgr_hnp.c, line 1573 and following?
2011/3/24 Ralph Castain
> You really don't want to do it that way - you'll create a major confusion
> in mpirun and the other daemons about who is where. Have you looked at the
> code in orte/mca/errmgr/hnp/errmgr_hnp.c, line 1573 and following?
>
I did not look at that, but i will do it right no
Guess I never considered that scenario when writing that code. The sysinfo
functionality isn't considered critical at this time, though there are some
changes coming that will make it more important.
Have to ponder the best solution - I'd rather not have configure fail just
because we don't fin
You really don't want to do it that way - you'll create a major confusion in
mpirun and the other daemons about who is where. Have you looked at the code in
orte/mca/errmgr/hnp/errmgr_hnp.c, line 1573 and following?
The ability to relocate a failed child process is already in the trunk - it
onl
Hello there,
I'm using OpenMPI for educational reasons. It works pretty fine under
GNU/Linux. I have both compiled it and downloaded it from the package
management system with no problems.
But I have trying to use it in other Unix systems as well. In these
systems /proc (NetBSD for instance) i
Hello @ll.
I'm trying to restart a child that has failed, now i'm catching the failed
child in the errmgr and then i'm packing the child and sending it to another
node who has to "adopt" it. Is there any way to do this with te actual
implementation? something like add_child. Because the i will hav
15 matches
Mail list logo
