You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@continuum.apache.org by "Corridor Software Developer (JIRA)" <ji...@codehaus.org> on 2005/11/29 05:09:06 UTC
[jira] Created: (CONTINUUM-483) Setting RUN_AS_USER causes startup script to fail.
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
[jira] Commented: (CONTINUUM-483) Setting RUN_AS_USER causes startup script to fail.
Posted by "Jason Lowmiller (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-483?page=comments#action_52295 ]
Jason Lowmiller commented on CONTINUUM-483:
-------------------------------------------
Emmanuel .. I believe it would yes! Let me know if it does, just for curiosity sake.
> 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
> 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
[jira] Commented: (CONTINUUM-483) Setting RUN_AS_USER causes startup script to fail.
Posted by "Corridor Software Developer (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (CONTINUUM-483) Setting RUN_AS_USER causes startup script to fail.
Posted by "Jason Lowmiller (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Closed: (CONTINUUM-483) Setting RUN_AS_USER causes startup script to fail.
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-483?page=all ]
Emmanuel Venisse closed CONTINUUM-483:
--------------------------------------
Assign To: Emmanuel Venisse
Resolution: Fixed
Fixed.
> 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
[jira] Updated: (CONTINUUM-483) Setting RUN_AS_USER causes startup script to fail.
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-483?page=all ]
Emmanuel Venisse updated CONTINUUM-483:
---------------------------------------
Fix Version: 1.0.2
> 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
> 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
[jira] Commented: (CONTINUUM-483) Setting RUN_AS_USER causes startup script to fail.
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-483?page=comments#action_52292 ]
Emmanuel Venisse commented on CONTINUUM-483:
--------------------------------------------
Is it fix CONTINUUM-410 too?
> 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
> 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