45bbf5b directed job submission stdout and stderr to the daemon stdout and stderr. This is usually a good thing, but at has the annoying habit of always reporting everything via stderr, e.g.:
[t0310.2013010100 job submission] job 58630 at 2013-11-11 10:20
[t0070.2013010100 job submission] job 58632 at 2013-11-11 10:20
[t0220.2013010100 job submission] job 58634 at 2013-11-11 10:20
which goes straight into the suite daemon stderr, whether the submission succeeded or not.
This makes the gcylc error notification (#692) useless for suites that heavily use at.
We should figure out a way to stop the pollution of the daemon stderr in the case of successful submissions. This could even just be at specific...
45bbf5b directed job submission stdout and stderr to the daemon stdout and stderr. This is usually a good thing, but
at
has the annoying habit of always reporting everything via stderr, e.g.:which goes straight into the suite daemon stderr, whether the submission succeeded or not.
This makes the gcylc error notification (#692) useless for suites that heavily use
at
.We should figure out a way to stop the pollution of the daemon stderr in the case of successful submissions. This could even just be
at
specific...