[ http://jira.codehaus.org/browse/CONTINUUM-483?page=comments#action_52897 ]
Corridor Software Developer commented on CONTINUUM-483: ------------------------------------------------------- I'd like to add for the sake of completeness that I ended with the following command: su - $RUN_AS_USER -c "exec $CMDNICE $WRAPPER_CMD $WRAPPER_CONF wrapper.pidfile=$PIDFILE wrapper.daemonize=TRUE" the -m was causing the root accounts environment to be used instead of my "continuum" user account. While this may by fine in other people's cases, it was causing the path to not include mvn or java since I don't have these defined for the root user. `su - continuum` resolved this. > Setting RUN_AS_USER causes startup script to fail. > -------------------------------------------------- > > Key: CONTINUUM-483 > URL: http://jira.codehaus.org/browse/CONTINUUM-483 > Project: Continuum > Type: Bug > Components: Core system > Versions: 1.0.1 > Environment: gentoo 2.6.5 kernel, bash 2.05 > Reporter: Corridor Software Developer > Assignee: Emmanuel Venisse > Fix For: 1.0.2 > > > If the run.sh script is modified to include a RUN_AS_USER, this line in the > script > su -m $RUN_AS_USER -c "exec $CMDNICE $WRAPPER_CMD $WRAPPER_CONF > wrapper.pidfile=$PIDFILE wrapper.daemonize=TRUE" > fails with the following error: > /bin/bash: continuum: No such file or directory > reducing the line yields the same error right down to the 'su -m user_name'. > However, if the -m is moved to beyond the user, everything works out: > su $RUN_AS_USER -m -c "exec $CMDNICE $WRAPPER_CMD $WRAPPER_CONF > wrapper.pidfile=$PIDFILE wrapper.daemonize=TRUE" > note that it occurs twice in the file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
