You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2021/06/21 16:05:56 UTC

[GitHub] [pulsar] BewareMyPower commented on pull request #10993: Modify a compilation problem caused by space in standalone.conf

BewareMyPower commented on pull request #10993:
URL: https://github.com/apache/pulsar/pull/10993#issuecomment-865158870


   @liangyepianzhou What's the need to run `source conf/standalone.conf`? `conf/standalone.conf` is just the configuration file that is read by pulsar standalone starter. For example,
   
   ```bash
   bin/pulsar-daemon start standalone
   ```
   
   It will read `conf/standalone.conf` as the configuration file of pulsar standalone by default.
   
   Or you can run
   
   ```bash
   PULSAR_STANDALONE_CONF=conf/standalone-2.conf bin/pulsar-daemon start standalone
   ```
   
   The it will read `conf/standalone-2.conf` as the configuration file of pulsar standalone by default.
   
   `conf/xxx.conf`s are all Java properties files, not a shell file that contains environment variables. Running `source conf/standalone.conf` is meaningless.
   
   In shell script, the variable assignment should not have any space around the `=`:
   
   ```bash
   VARIABLE=hello # OK
   VARIABLE = hello # Error
   ```
   
   But in Java properties file, spaces around `=` are okay.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org