You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2015/10/09 14:05:27 UTC

[jira] [Commented] (KARAF-3898) The same setenv used from all scripts, but should set different variable values

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

Jean-Baptiste Onofré commented on KARAF-3898:
---------------------------------------------

It does: KARAF_SCRIPT variable is defined by the script before calling setenv. So setenv can check the value of KARAF_SCRIPT and adapt accordingly to the script in use.

> The same setenv used from all scripts, but should set different variable values
> -------------------------------------------------------------------------------
>
>                 Key: KARAF-3898
>                 URL: https://issues.apache.org/jira/browse/KARAF-3898
>             Project: Karaf
>          Issue Type: Improvement
>    Affects Versions: 3.0.4
>            Reporter: Sergey 
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>             Fix For: 4.0.2, 3.0.6
>
>
> For example: JAVA_MAX_MEM=16g is ok for using from start.sh, but we don't need 16Gb to stop server. And it can prevent stop.sh from starting if we have only about 16Gb available.



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