daitss/core — Issue #622: submit command needs a non-verbose option
Author: lydiam
Created: 2012-01-23 21:23:13+00:00
State: open

With the new ACLs and sudo -u daitss requirements for running submit, there's no way to prevent the submit command from sending output to your terminal session, even when submit is running in the background. This requires DAITSS Operators to open a new terminal session in order to continue working on the server where the submit command was issued.

An example from Ripple:

[lydiam@ripple submit-direct]$ sudo -u daitss submit --username daitss --password daitss --source XDRIVE --path /var/daitss/ops/FDA_benchmarks/AD_HOC --batch BGtest3
2012-01-23 16:19:57 INFO Mon Jan 23 16:19:57 -0500 2012 -- FDA00067232_00001 -- submitted successfully: EJU5GDIDU_9VBF2K
(ctl+Z issued)
[1]+ Stopped sudo -u daitss submit --username daitss --password daitss --source XDRIVE --path /var/daitss/ops/FDA_benchmarks/AD_HOC --batch BGtest3
[lydiam@ripple submit-direct]$ bg
[1]+ sudo -u daitss submit --username daitss --password daitss --source XDRIVE --path /var/daitss/ops/FDA_benchmarks/AD_HOC --batch BGtest3 &
[lydiam@ripple submit-direct]$ 2012-01-23 16:20:22 INFO Mon Jan 23 16:20:22 -0500 2012 -- FDA00028308_00127 -- submitted successfully: EA9Z5ALJC_ZTU0CN

Also: logging out of the terminal session where the submit command was issued and then backgrounded causes the process to stop - would that have also been the case using "&" to background the process?