You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Philip Brown (JIRA)" <ji...@apache.org> on 2019/02/01 17:50:00 UTC
[jira] [Created] (DIRSERVER-2265) better way to change RUN_AS_USER
Philip Brown created DIRSERVER-2265:
---------------------------------------
Summary: better way to change RUN_AS_USER
Key: DIRSERVER-2265
URL: https://issues.apache.org/jira/browse/DIRSERVER-2265
Project: Directory ApacheDS
Issue Type: Bug
Components: core
Affects Versions: 2.0.0.AM25
Reporter: Philip Brown
If you want to actually use the standard ports like 389, the typical reaction would be to change the value of RUN_AS_USER, or remove the value.
Trouble is, seems like the currently expected way to do that, is to edit the script
(as implied by the comments)
But.. the apacheds/bin/apacheds script is packages. So changes will get blown away on update.
The wrapper thingie checks for instance-specific values in $INSTANCE_DIRECTORY/conf/wrapper.conf
Would be nice if apacheds script did something similar.
Heck, here's a potential diff patch.
67a
# Allow for overrides of values above, per instance
test -f $INSTANCE_DIRECTORY/conf/apacheds.vars && source $INSTANCE_DIRECTORY/conf/apacheds.vars
.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)