continuum-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Corridor Software Developer (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-483) Setting RUN_AS_USER causes startup script to fail.
Date Tue, 06 Dec 2005 18:42:04 GMT
    [ ] 

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

> Setting RUN_AS_USER causes startup script to fail.
> --------------------------------------------------
>          Key: CONTINUUM-483
>          URL:
>      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 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
> 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
> 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:
For more information on JIRA, see:

View raw message