-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all,
Apologies for having dropped out of the thread, night intervened here. ;-) On 08/05/14 00:45, Ralph Castain wrote: > Okay, then we'll just have to develop a workaround for all those > Slurm releases where PMI-2 is borked :-( Do you know what these releases are? Are we talking 2.6.x or 14.03? The 14.03 series has had a fair few rapid point releases and doesn't appear to be anywhere as near as stable as 2.6 was when it came out. :-( > FWIW: I think people misunderstood my statement. I specifically > did *not* propose to *lose* PMI-2 support. I suggested that we > change it to "on-by-request" instead of the current "on-by-default" > so we wouldn't keep getting asked about PMI-2 bugs in Slurm. Once > the Slurm implementation stabilized, then we could reverse that > policy. > > However, given that both you and Chris appear to prefer to keep it > "on-by-default", we'll see if we can find a way to detect that > PMI-2 is broken and then fall back to PMI-1. My intention was to provide the data that led us to want PMI2, but if configure had an option to enable PMI2 by default so that only those who requested it got it then I'd be more than happy - we'd just add it to our script to build it. All the best! Chris - -- Christopher Samuel Senior Systems Administrator VLSCI - Victorian Life Sciences Computation Initiative Email: sam...@unimelb.edu.au Phone: +61 (0)3 903 55545 http://www.vlsci.org.au/ http://twitter.com/vlsci -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlNq2poACgkQO2KABBYQAh+7DwCfeahirvoQ9Wom4VNhJIIdufeP 7uIAnAruTnXZBn6HXhuMAlzzSsoKkXlt =OvH4 -----END PGP SIGNATURE-----
