[
https://issues.apache.org/jira/browse/GEODE-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14612588#comment-14612588
]
Kirk Lund commented on GEODE-47:
--------------------------------
The LocatorLauncher and ServerLauncher classes can be used as Java main classes
for launching a Locator or Server in the foreground. GFSH is using these as the
Java main for new background JVMs. To do the same simply use the main in either
class:
{code}
java -cp $GEODE/lib/gemfire-core-dependencies.jar
com.gemstone.gemfire.distributed.ServerLauncher start server1
{code}
Valid commands for ServerLauncher include:
{code}
start <member-name> [--assign-buckets] [--disable-default-server] [--rebalance]
[--server-bind-address=<IP-address>] [--server-port=<port>] [--force] [--debug]
[--help]
{code}
{code}
status [--member=<member-ID/Name>] [--pid=<process-ID>]
[--dir=<Server-working-directory>] [--debug] [--help]
{code}
{code}
stop [--member=<member-ID/Name>] [--pid=<process-ID>]
[--dir=<Server-working-directory>] [--debug] [--help]
{code}
{code}
version
{code}
> GFSH can't start servers in foreground
> --------------------------------------
>
> Key: GEODE-47
> URL: https://issues.apache.org/jira/browse/GEODE-47
> Project: Geode
> Issue Type: Bug
> Components: management & tools
> Reporter: William Markito Oliveira
> Priority: Minor
> Labels: gfsh
>
> There are certain cases where users may want to use gfsh and start members
> (locator or servers) in foreground.
> In old scripts there was an alternative to have servers started in foreground
> but that's not available anymore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
