You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Sergey (JIRA)" <ji...@apache.org> on 2015/09/23 13:31:04 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=14904362#comment-14904362 ] 

Sergey  commented on KARAF-3898:
--------------------------------

BTW, looks like it was implemented partially, but not completed:

karaf.sh:
{code}
    # Set Debug options if enabled
    if [ "x$KARAF_DEBUG" != "x" ]; then
        # Ignore DEBUG in case of stop or client mode
        if [ "x$MODE" = "xstop" ]; then
            return
        fi
{code}

status.sh
{code}
KARAF_SCRIPT="status"
export KARAF_SCRIPT
if [ -f "$DIRNAME/setenv" ]; then
  . "$DIRNAME/setenv"
fi
{code}

Should set $1 here:
{code}
  . "$DIRNAME/setenv" status
{code}

but didn't.

> 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
>
> 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)