You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steve Rowe (JIRA)" <ji...@apache.org> on 2018/04/17 20:02:00 UTC

[jira] [Resolved] (SOLR-12231) /etc/init.d/solr problem

     [ https://issues.apache.org/jira/browse/SOLR-12231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Rowe resolved SOLR-12231.
-------------------------------
    Resolution: Not A Problem
      Assignee: Steve Rowe

This is not a syntax error.  This syntax assigns a value to an environment variable in the process created for the following command.

I couldn't find info on this capability in the Bash manual, but here is info from [https://help.ubuntu.com/community/EnvironmentVariables]:

{quote}
h2. Bash's quick assignment and inheritance trick

The bash shell has a trick to allow us to set one or more environment variables and run a child process with single command. For example, in order to set the "LANGUAGE" and "FOO" environment variables and then run "gedit", we would use the following command:

{noformat}
LANGUAGE=he FOO=bar gedit
{noformat}

Note: When using this command, the new values are only assigned to the environment variables of the child process (in this case gedit). The variables of the shell retain their original values. For instance, in the example above, the value of "LANGUAGE" will not change from its original value, as far as subsequent commands to the shell are concerned.
{quote}

> /etc/init.d/solr problem
> ------------------------
>
>                 Key: SOLR-12231
>                 URL: https://issues.apache.org/jira/browse/SOLR-12231
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: scripts and tools
>    Affects Versions: 7.3
>         Environment: Centos 7.4 
> java-1.8.0-openjdk
>            Reporter: Lihua Wang
>            Assignee: Steve Rowe
>            Priority: Minor
>
> I noticed that there are a couple of minor issues with the init.d script in pretty much every version. 
> Basically, a semicolon (or an escaped semicolon) is missing in the *{color:#205081}BLUE{color}* lines blow:
>  
> if [ -n "$RUNAS" ]; then
>  {color:#205081}su -c "SOLR_INCLUDE=\"$SOLR_ENV\" \"$SOLR_INSTALL_DIR/bin/solr\" $SOLR_CMD" - "$RUNAS"{color}
>  else
>  {color:#205081}SOLR_INCLUDE="$SOLR_ENV" "$SOLR_INSTALL_DIR/bin/solr" "$SOLR_CMD"{color}
>  fi
>  
> *With the {color:#d04437}added semicolons{color} (escaped where necessary), the code would look like:* 
> if [ -n "$RUNAS" ]; then
>  *{color:#8eb021}{color:#8eb021}su -c "SOLR_INCLUDE=\"$SOLR_ENV\"{color:#d04437}\;{color}{color} \"$SOLR_INSTALL_DIR/bin/solr\" $SOLR_CMD" - "$RUNAS"{color}{color:#8eb021}*{color}*
>  *else*
>  *{color:#8eb021}*SOLR_INCLUDE="$SOLR_ENV"{color:#d04437};{color}{color}{color:#8eb021} "$SOLR_INSTALL_DIR/bin/solr" "$SOLR_CMD"{color}*
>  fi
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org