You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org> on 2006/03/15 16:47:30 UTC
[jira] Closed: (CONTINUUM-554) Fix RUN_AS_USER feature for UNIX
environments (linux, solaris,macos)
[ http://jira.codehaus.org/browse/CONTINUUM-554?page=all ]
Emmanuel Venisse closed CONTINUUM-554:
--------------------------------------
Assign To: Emmanuel Venisse
Resolution: Fixed
Fix Version: 1.0.3
Applied. Thanks.
> Fix RUN_AS_USER feature for UNIX environments (linux, solaris,macos)
> --------------------------------------------------------------------
>
> Key: CONTINUUM-554
> URL: http://jira.codehaus.org/browse/CONTINUUM-554
> Project: Continuum
> Type: Bug
> Components: Core system
> Versions: 1.0.2
> Environment: any unix like OS running continuum as non root user.
> Reporter: Rainer Pruy
> Assignee: Emmanuel Venisse
> Fix For: 1.0.3
> Attachments: DIFF
>
>
> When RUN_AS_USER is specified in the run.sh script continuum will not start.
> This is caused by a change in the current directory resulting from calling "su - .....".
> In the regular (non RUN_AS_USER) case, the current directory is changed to the os specific calling directory "bin/<OS>/".
> After calling "su - ..." the current directory is the home directory of the target user.
> For fixing the following two possibilities come to mind:
> 1: change to the correct directory within the command passed to "su"
> (See the enclosed patch for bin/linux/run.sh" a similar patch may be applied for solaris and macos)
> 2. avoid using "su - "
> Calling "su" without "-" option will preserve the current environment and not change the current directory.
> I personally prefer method '1'. Usually the run user will be a dedicated user for running continuum. Using "-" option will establish a default environment for this user. Theat is easy to be controlled and configured and avoids conflicts with other applications.
--
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