[
https://issues.apache.org/jira/browse/GEODE-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14612590#comment-14612590
]
Kirk Lund commented on GEODE-47:
--------------------------------
Here's a more complex example in script form from John Blum:
{code}
#!/bin/bash
launcherCommand=$1
serverName=$2
serverDir=$3
serverPid=$3
serverPort=$3
serverBindAddress=$4
[[ -d "$serverDir" ]] && serverDirOption="--dir=$serverDir"
pidFound=`ps -o pid | grep -c "${serverPid:-x}"`
[[ ! "$pidFound" -eq "0" ]] && serverPidOption="--pid=$serverPid"
[[ ! -z "$serverPort" ]] && serverPortOption="--server-port=$serverPort"
[[ ! -z "$serverBindAddress" ]] &&
serverBindAddressSystemProperty="-Dgemfire.bind-address=$serverBindAddress"
java -Dgemfire.locators=localhost[11235] -Dgemfire.log-level=config
-Dgemfire.launcher.registerSignalHandlers=true
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
$serverBindAddressSystemProperty -classpath
"$GEODE/lib/gemfire-core-dependencies.jar"
com.gemstone.gemfire.distributed.ServerLauncher --redirect-output
$launcherCommand $serverName $serverDirOption $serverPidOption $serverPortOption
{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)
