Hello,
When i try to compile openmpi-1.2.6.tar.bz2 on my computer with ifort
Compilier.My system is Red Hat4.6 86x64.But some mistakes happen when the
process of configuring.Mistakes as follows:
$./configure --prefix=~/haowp/opt/openmpi FC=ifort F90=ifort
.
..
*** GNU libltdl setup
Hello,
When i try to compile openmpi-1.2.6.tar.bz2 on my computer with ifort
Compilier.My system is Red Hat4.6 86x64.But some mistakes happen when the
process of configuring.Mistakes as follows:
$./configure --prefix=~/haowp/opt/openmpi FC=ifort F90=ifort
.
..
*** GNU libltdl setu
> That text message is hard-coded (and apparently out of date); it
> does not show the current value.
>
> I agree that that is misleading. This error message needs to be
> improved.
OK, good to have that clarified Jeff, cheers.
> This might suggest a hardware issue; let us know what you find.
Ve
I would appreciate trying to fix the multi-word argument to orte_launch_agent,
unless you've already fixed it in a later series in which case I could update.
My workaround with the setuid applied to a copied executable doesn't work for
other applications that run on our clusters ( I mean their
Hi Ed
I finally had some time to dig around a little. I believe we could make this
work if I fix the multi-word cmd line param issue. Either "newgrp" or "sg"
should resolve the problem - both are user-level cmds.
Up to you - let me know if you want me to pursue this.
Ralph
On Sep 14, 2011, at
Thank you - I did pursue this kind of workaround, and it worked, but you'll be
happy to know that nothing had to be owned by root.
ASIDE
Just to remind: The job script is a shell script that invokes mpirun; the job
script itself is run with as the correct user, but the group id may be cha
LinkedIn
Mudassar Majeed requested to add you as a connection on LinkedIn:
--
Mohan,
I'd like to add you to my professional network on LinkedIn.
- Mudassar
Accept invitation from Mudassar Majeed
http://www.linkedin.com/e/kq0fyp-gsksu
You could set the setuid bit on the application and chown it to root?? It
is about as secure as anything else that has been described thus far. As a
system admin, I cringe at the thought of anything that would allow something
to run as someone else, so there would have to be a pretty good
justif
Am 14.09.2011 um 19:02 schrieb Blosch, Edwin L:
> Thanks for trying.
>
> Do you feel that this is an impossible request without the assistance of some
> process running as root, for example, as Reuti mentioned, the daemons of a
> job scheduler? Or are you saying it will just not be as straigh
On Sep 14, 2011, at 1:23 PM, Blosch, Edwin L wrote:
>
>> Try -mca orte_launch_agent "sg N orted", where N is the desired group ID.
>
> There is a catch in the way the orted process is started.
>
> I get messages like this:
>
> bash: sg /home/install/openmpi/bin/(null) --daemonize -mca ess en
> Try -mca orte_launch_agent "sg N orted", where N is the desired group ID.
There is a catch in the way the orted process is started.
I get messages like this:
bash: sg /home/install/openmpi/bin/(null) --daemonize -mca ess env -mca
orte_ess_jobid 3913285632 -mca orte_ess_vpid 9 -mca orte_ess_
On Sep 14, 2011, at 11:02 AM, Blosch, Edwin L wrote:
> Thanks for trying.
>
> Do you feel that this is an impossible request without the assistance of some
> process running as root, for example, as Reuti mentioned, the daemons of a
> job scheduler? Or are you saying it will just not be as s
Thanks for trying.
Do you feel that this is an impossible request without the assistance of some
process running as root, for example, as Reuti mentioned, the daemons of a job
scheduler? Or are you saying it will just not be as straightforward as calling
setgid as you had hoped?
Also, do you
- Original Message -
> On Sep 12, 2011, at 10:44 PM, Steve Jones wrote:
>
> > We've run into an IO issue with 1.4.1 and earlier versions. We're
> > able to reproduce the issue in around 120 lines of code to help, I'd
> > like to find if there's something we're simply doing incorrectly
> >
- Original Message -
> On Mon, Sep 12, 2011 at 07:44:25PM -0700, Steve Jones wrote:
> > Hi.
> >
> > We've run into an IO issue with 1.4.1 and earlier versions. We're
> > able to reproduce the issue in around 120 lines of code to help.
>
> Hi Steve Jones
>
> I'm the ROMIO maintainer, and a
On Sep 14, 2011, at 9:39 AM, Blosch, Edwin L wrote:
> Thanks, Ralph,
>
> I get the failure messages, unfortunately:
>
> setgid FAILED
> setgid FAILED
> setgid FAILED
>
> I actually had attempted to call setgid from within the application
> previously, which looks similar to what you've done,
Hi,
Am 14.09.2011 um 17:39 schrieb Blosch, Edwin L:
> Thanks, Ralph,
>
> I get the failure messages, unfortunately:
>
> setgid FAILED
> setgid FAILED
> setgid FAILED
N.B.: This would be a side effect of the tight integration to do it
automatcially for all slave tasks.
-- Reuti
> I actually
Thanks, Ralph,
I get the failure messages, unfortunately:
setgid FAILED
setgid FAILED
setgid FAILED
I actually had attempted to call setgid from within the application previously,
which looks similar to what you've done, but it failed. That was when I
initiated the post to the mailing list. My
You would recommend you to verify, that you don't have any bad cables or ports
in your IB network. You may to use one of OFA network check tools, for example
ibdiagnet.
Pavel (Pasha) Shamis
---
Application Performance Tools Group
Computer Science and Math Division
Oak Ridge National Laboratory
The attached should set the gid of the remote daemons (and their children) to
the gid of mpirun. No cmd line option or anything is required - it will just
always do it.
Would you mind giving it a try?
Please let me know if/how it works.
14setgid.diff
Description: Binary data
On Sep 8, 2011
Ah! Are you using MPI-thread-multiple?
Sent from my phone. No type good.
On Sep 14, 2011, at 5:28 AM, "devendra rai" wrote:
> Hello MPI Forum, Jeff
>
> Well, the problem is not with incorrect arguments with MPI_Ssend(...) and/or
> MPI_Recv(...). I confirmed this. Also, if there were any ob
On Sep 13, 2011, at 6:33 PM, kevin.buck...@ecs.vuw.ac.nz wrote:
> there have been two runs of jobs that invoked the mpirun using these
> OpenMPI parameter setting flags (basically, these mimic what I have
> in the global config file)
>
> -mca btl_openib_ib_timeout 20 -mca btl_openib_ib_min_rnr_ti
Hello MPI Forum, Jeff
Well, the problem is not with incorrect arguments with MPI_Ssend(...) and/or
MPI_Recv(...). I confirmed this. Also, if there were any obvious programming
and logical errors, I would never have any successful run. In fact, I am having
some runs which go through successful
23 matches
Mail list logo
