Notes for using sudo (AppServers):

• On LAB systems
• On production systems

The InfoRouter AppServer is running under a user called 'tomcat'. This user must own all relevant
files for the AppServer to function correctly.

The install and restart scripts LB_install and CL_restart ensure that the execution
environment is setup correctly for the AppServer [ available on DataCenter mgt-server ].

When using e.g. "sudo -u tomcat vi inforouter.xml" on an appserver the ownership of 'inforouter.xml'
is trivially ensured to remain as 'tomcat' (as well as creating an audit trail).

LAB systems

For lab systems you should log in on mgt-dtu.soonr.com with your personalized Soonr account -
from there you can log in on any (lab) appserver - still using your own account.

When on a LAB appserver you can choose to use 'sudo -u tomcat' to run necessary commands in the
same manner as on a production systems, OR:

• change effective user to tomcat using 'sudo -iu tomcat'
• you only need 'sudo -iu tomcat' once per login-session
• when acting as tomcat user: startLAB* and startTERRACOTTA still require sudo -E

Production systems

For a production system you can login on an appserver using your own account via a relevant mgt-server,
but once on an appserver, access to alter and inspect files must as a general rule happen via the use of

• "sudo -u tomcat SOME_COMMAND"

The current list of commands supported to run as 'sudo -u tomcat':

• /roothome/install-server
• vi, cp, mv, mkdir, rm
• gzip, grep, zgrep, egrep, zegrep
• less, zless(+)
• cat, zcat

• zcat, zgrep, egrep, zegrep, zless(+)

The current list of commands supported to run as 'sudo -E SOME_COMMAND' (i.e. as root):

• /etc/init.d/startSERVER (e.g. /etc/init.d/startVIP-1A)
• /etc/init.d/startTERRACOTTA

• sudo -E -u tomcat zless FILE.gz