[jira] [Commented] (DIRSERVER-2265) better way to change RUN_AS_USER

["Emmanuel Lecharny (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DIRSERVER-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16861517#comment-16861517 ] 

Emmanuel Lecharny commented on DIRSERVER-2265:
----------------------------------------------

Actually, the right way to do that (allowing a user to run *apacheds* under port *389*) would be to add this user into the *sudo* group. That also means the server has to be stated with *sudo*.

The scripts should reflect that.

> 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: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org