gsh has STDOUT that is not helpful for cron jobs to send email from STDOUT from processes

Starting gsh always outputs some STDOUT and can be "noise" for a cron job's output.

example:

"
Using GROUPER_HOME: /opt/....apiBinary-2.3.0/bin/..
Using GROUPER_CONF: /opt/....apiBinary-2.3.0/bin/../conf
Using JAVA: /opt/java/bin/java
using MEMORY: ....
Grouper starting up: version: 2.3.0, build date: null, env: PROD
grouper.properties read from: /opt/....apiBinary-2.3.0/conf/grouper.properties
Grouper current directory is: /opt/....apiBinary-2.3.0/bin
log4j.properties read from: /opt/....apiBinary-2.3.0/conf/log4j.properties
Grouper is logging to file: /app/.....apiBinary/grouper_error.log, at min level WARN for package: edu.internet2.middleware.grouper, based on log4j.properties
grouper.hibernate.properties: /opt/....apiBinary-2.3.0/conf/grouper.hibernate.properties
grouper.hibernate.properties: ....
subject.properties read from: /opt/....apiBinary-2.3.0/conf/subject.properties
sources.xml read from: /opt/.....apiBinary-2.3.0/conf/sources.xml
sources configured in: sources.xml
sources.xml groupersource id: g:gsa
sources.xml groupersource id: grouperEntities
sources.xml jdbc source id: jdbc: GrouperJdbcConnectionProvider
sources.xml ldap source id: .....
Type help() for instructions
"

There is also "command prompts" to suppress as well:
"
groovy:000> :
"