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

ASF GitHub Bot commented on CLOUDSTACK-7476:
--------------------------------------------

Github user DaanHoogland commented on the pull request:

    https://github.com/apache/cloudstack/pull/17#issuecomment-54790328
  
    Leo, you are right but if it is in 4.3 not putting it in 4.4 would make it
    a double behavioural change from a user perspective. So I will look at
    cherry-picking it anyway
    
    
    On Mon, Sep 8, 2014 at 9:38 AM, Leo Simons <[email protected]> wrote:
    
    > Hey Daan, *this* change is fine&done as-is. Like Rajani mentioned, the
    > other changes to that file could be ported, too. I'm +0 on that -- on the
    > one hand, it's a good change and I can't see any way that it would ever
    > break anything, on the other hand it's a (however minor) behavioral change
    > so I personally wouldn't put that in a point release.
    >
    > —
    > Reply to this email directly or view it on GitHub
    > <https://github.com/apache/cloudstack/pull/17#issuecomment-54785217>.
    >
    
    
    
    -- 
    Daan


> centos cloudstack-usage script does not always pass along $JAVA_HOME
> --------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7476
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7476
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Usage
>    Affects Versions: 4.5.0
>         Environment: secured centos/redhat
>            Reporter: Leo Simons
>             Fix For: 4.5.0
>
>
> /etc/init.d/cloudstack-usage finds a $JAVA_HOME and makes sure the 
> environment variable is set, then assumes this variable will be picked up by 
> JSVC.
> However, on a secured environment (selinux w/ env_reset enabled in sudoers), 
> the runuser command that is invoked by the daemon() function does not pass 
> along environment variables, so $JAVA_HOME is empty, and JSVC falls back to 
> its default behavior, which may not find java or may not find the intended 
> java.
> The simple solution is to pass -home to JSVC, passing it on the command line 
> instead of as an environment variable.
> I'll provide a patch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to