By popular acclaim we keep supporting the old behaviour for historical reasons. The fix will be available in 14.03.4. The commit is 6aadcf15355dfe.

On 05/21/2014 04:54 AM, Bill Barth wrote:

Yes, that's going to be a big problem for us to. It's good that 2.6 is
working well for us.

Any chance we can get the old behavior back?

Best
Bill.
--
Bill Barth, Ph.D., Director, HPC
[email protected]        |   Phone: (512) 232-7069
Office: ROC 1.435             |   Fax:   (512) 475-9445







On 5/21/14 12:13 AM, "Christopher Samuel" <[email protected]> wrote:


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 21/05/14 05:56, David Bigagli wrote:

Yes, it is a change in behaviour. There was a fix in the I/O module
that unfortunately introduced this side effect.

Oh dear, that's going to be a fun bit of user re-education if we go to
14.x.  Hopefully we can abstract it out into our "sinteractive" script
somehow..

All the best,
Chris
- --
Christopher Samuel        Senior Systems Administrator
VLSCI - Victorian Life Sciences Computation Initiative
Email: [email protected] 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/

iEYEARECAAYFAlN8NbsACgkQO2KABBYQAh8T1QCfULRkNOizFfJuhwxdlHVdz/Gn
HzAAn1fjcKNq8jxJme9DiuFMIe2dG9f3
=ogC9
-----END PGP SIGNATURE-----

--

Thanks,
      /David/Bigagli

www.schedmd.com

Reply via email to