Great! Thank you so much! Roman.
On Sun, Aug 16, 2015 at 10:31 AM, Kirk Lund <[email protected]> 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 <[email protected]> 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" <[email protected]> >> wrote: >>> >>> Specify --properties-file=<path to file> when you start components. >>> >>> >>> >>> ________________________________ >>> From: Roman Shaposhnik <[email protected]> >>> To: [email protected] >>> 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. >>> >>> >
