You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geode.apache.org by Roman Shaposhnik <rv...@apache.org> on 2015/08/16 09:11:22 UTC
How to pick up config/gemfire.properties file?
Hi!
it seems that when using gfsh to start locator/server
they don't pick up config/gemfire.properties by default.
What do I need to do to make it happen?
Thanks,
Roman.
Re: How to pick up config/gemfire.properties file?
Posted by John Blum <jb...@pivotal.io>.
Note, the options are relative to "Gfsh's" working directory, not the
GemFire process. Also note, the "name" (as specified with "start
[locator|server] --name=X") is the name of the GemFire member, not the
actual JVM process.
Gfsh will pass the "location" (file system path) to the forked GemFire
process by way of (GemFire) System property (
http://gemfire.docs.pivotal.io/latest/userguide/index.html#reference/topics/gemfire_properties.html).
The GemFire process will look for gemfire.properties/cache.xml, etc
relative to it's own working directory unless an absolute path is given.
GemFire does use "default" locations when looking for certain configuration
files: working dir, user home dir, classpath. Though these default
locations can be used, it is recommended you specify the location of
configuration files explicitly. Unexpected things happen when you forget
that you left a configuration file (.properties or cache.xml) in you home
directory, for instance.
-j
On Sun, Aug 16, 2015 at 10:31 AM, Kirk Lund <ki...@gmail.com> wrote:
> By default, GFSH will start the locator or server in a subdir of the same
> name as the process. Ex: "start locator --name=locator1" will use
> ./locator1 as the current working dir for that process.
>
> 1) if the subdir does not exist use:
>
> gfsh>start locator --name=locator1 --properties-file=<path to file>
>
> 2) if the subdir does exist (either you created or GFSH did previously):
>
> copy the gemfire.properties to that subdir if you want to avoid specifying
> it every time
>
> gfsh>start locator --name=locator1
>
> On Sunday, August 16, 2015, Michael Stolz <ms...@pivotal.io> wrote:
>
>> Or put the gemfire.properties file in the folder where the server will
>> home itself. Normally same name as the name you give the server.
>>
>> --
>> Mike Stolz
>> Principal Technical Account Manager
>> Mobile: 631-835-4771
>> On Aug 16, 2015 3:18 AM, "Catherine Johnson" <ca...@yahoo.com>
>> wrote:
>>
>>> Specify --properties-file=<path to file> when you start components.
>>>
>>>
>>>
>>> ------------------------------
>>> *From:* Roman Shaposhnik <rv...@apache.org>
>>> *To:* user@geode.incubator.apache.org
>>> *Sent:* Sunday, August 16, 2015 12:11 AM
>>> *Subject:* How to pick up config/gemfire.properties file?
>>>
>>> Hi!
>>>
>>> it seems that when using gfsh to start locator/server
>>> they don't pick up config/gemfire.properties by default.
>>> What do I need to do to make it happen?
>>>
>>> Thanks,
>>> Roman.
>>>
>>>
>>>
--
-John
503-504-8657
john.blum10101 (skype)
Re: How to pick up config/gemfire.properties file?
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
Great! Thank you so much!
Roman.
On Sun, Aug 16, 2015 at 10:31 AM, Kirk Lund <ki...@gmail.com> wrote:
> By default, GFSH will start the locator or server in a subdir of the same
> name as the process. Ex: "start locator --name=locator1" will use ./locator1
> as the current working dir for that process.
>
> 1) if the subdir does not exist use:
>
> gfsh>start locator --name=locator1 --properties-file=<path to file>
>
> 2) if the subdir does exist (either you created or GFSH did previously):
>
> copy the gemfire.properties to that subdir if you want to avoid specifying
> it every time
>
> gfsh>start locator --name=locator1
>
> On Sunday, August 16, 2015, Michael Stolz <ms...@pivotal.io> wrote:
>>
>> Or put the gemfire.properties file in the folder where the server will
>> home itself. Normally same name as the name you give the server.
>>
>> --
>> Mike Stolz
>> Principal Technical Account Manager
>> Mobile: 631-835-4771
>>
>> On Aug 16, 2015 3:18 AM, "Catherine Johnson" <ca...@yahoo.com>
>> wrote:
>>>
>>> Specify --properties-file=<path to file> when you start components.
>>>
>>>
>>>
>>> ________________________________
>>> From: Roman Shaposhnik <rv...@apache.org>
>>> To: user@geode.incubator.apache.org
>>> Sent: Sunday, August 16, 2015 12:11 AM
>>> Subject: How to pick up config/gemfire.properties file?
>>>
>>> Hi!
>>>
>>> it seems that when using gfsh to start locator/server
>>> they don't pick up config/gemfire.properties by default.
>>> What do I need to do to make it happen?
>>>
>>> Thanks,
>>> Roman.
>>>
>>>
>
Re: How to pick up config/gemfire.properties file?
Posted by Kirk Lund <ki...@gmail.com>.
By default, GFSH will start the locator or server in a subdir of the same
name as the process. Ex: "start locator --name=locator1" will use
./locator1 as the current working dir for that process.
1) if the subdir does not exist use:
gfsh>start locator --name=locator1 --properties-file=<path to file>
2) if the subdir does exist (either you created or GFSH did previously):
copy the gemfire.properties to that subdir if you want to avoid specifying
it every time
gfsh>start locator --name=locator1
On Sunday, August 16, 2015, Michael Stolz <ms...@pivotal.io> wrote:
> Or put the gemfire.properties file in the folder where the server will
> home itself. Normally same name as the name you give the server.
>
> --
> Mike Stolz
> Principal Technical Account Manager
> Mobile: 631-835-4771
> On Aug 16, 2015 3:18 AM, "Catherine Johnson" <catherinej30@yahoo.com
> <javascript:_e(%7B%7D,'cvml','catherinej30@yahoo.com');>> wrote:
>
>> Specify --properties-file=<path to file> when you start components.
>>
>>
>>
>> ------------------------------
>> *From:* Roman Shaposhnik <rvs@apache.org
>> <javascript:_e(%7B%7D,'cvml','rvs@apache.org');>>
>> *To:* user@geode.incubator.apache.org
>> <javascript:_e(%7B%7D,'cvml','user@geode.incubator.apache.org');>
>> *Sent:* Sunday, August 16, 2015 12:11 AM
>> *Subject:* How to pick up config/gemfire.properties file?
>>
>> Hi!
>>
>> it seems that when using gfsh to start locator/server
>> they don't pick up config/gemfire.properties by default.
>> What do I need to do to make it happen?
>>
>> Thanks,
>> Roman.
>>
>>
>>
Re: How to pick up config/gemfire.properties file?
Posted by Michael Stolz <ms...@pivotal.io>.
Or put the gemfire.properties file in the folder where the server will home
itself. Normally same name as the name you give the server.
--
Mike Stolz
Principal Technical Account Manager
Mobile: 631-835-4771
On Aug 16, 2015 3:18 AM, "Catherine Johnson" <ca...@yahoo.com> wrote:
> Specify --properties-file=<path to file> when you start components.
>
>
>
> ------------------------------
> *From:* Roman Shaposhnik <rv...@apache.org>
> *To:* user@geode.incubator.apache.org
> *Sent:* Sunday, August 16, 2015 12:11 AM
> *Subject:* How to pick up config/gemfire.properties file?
>
> Hi!
>
> it seems that when using gfsh to start locator/server
> they don't pick up config/gemfire.properties by default.
> What do I need to do to make it happen?
>
> Thanks,
> Roman.
>
>
>
Re: How to pick up config/gemfire.properties file?
Posted by Catherine Johnson <ca...@yahoo.com>.
Specify --properties-file=<path to file> when you start components.
From: Roman Shaposhnik <rv...@apache.org>
To: user@geode.incubator.apache.org
Sent: Sunday, August 16, 2015 12:11 AM
Subject: How to pick up config/gemfire.properties file?
Hi!
it seems that when using gfsh to start locator/server
they don't pick up config/gemfire.properties by default.
What do I need to do to make it happen?
Thanks,
Roman.