You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@continuum.apache.org by "Jason Lowmiller (JIRA)" <ji...@codehaus.org> on 2005/11/29 07:22:06 UTC

[jira] Commented: (CONTINUUM-483) Setting RUN_AS_USER causes startup script to fail.

    [ http://jira.codehaus.org/browse/CONTINUUM-483?page=comments#action_52272 ] 

Jason Lowmiller commented on CONTINUUM-483:
-------------------------------------------

Have also ran into this issue.  Perhaps if this were added to the FAQ it would have saved some time.  Thx

> 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

>
>
> 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