Open GoogleCodeExporter opened 9 years ago
Indeed, GAMESS jobs are submitted with stdout+stderr merged into one, this is
why the "-e" and "-o" options have the same effect.
Should we print a warning telling users that the job did not request separate
stdout and stderr streams?
(I personally would be in favor of submitting *any* job with merged streams and
get rid of the two options; I have yet to see a scientific application that
uses stderr properly. But this is rather a different issue.)
Original comment by riccardo.murri@gmail.com
on 31 Jan 2011 at 2:43
Original comment by riccardo.murri@gmail.com
on 8 Feb 2011 at 10:30
Original issue reported on code.google.com by
timm.reu...@uzh.ch
on 28 Jan 2011 at 2:19