[
https://issues.apache.org/jira/browse/DIRSERVER-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16861523#comment-16861523
]
Philip Brown commented on DIRSERVER-2265:
-----------------------------------------
there's more than one way to address the issue of "user run on port 389".
keep in mind that it is also possible to simply allow a non-root user to
directly run stuff on low ports, if the sysadmin chooses to do so.
> 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: installer-plugin
> Affects Versions: 2.0.0.AM25
> Reporter: Philip Brown
> Priority: Minor
>
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
