Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.0.2
-
Fix Version/s: 1.0.3
-
Component/s: Core system
-
Labels:None
-
Environment:any unix like OS running continuum as non root user.
-
Complexity:Intermediate
-
Number of attachments :
Description
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.
I can confirm this patch works like a charm..