1.1.1

DescriptionOption
members have booted and the member has finished synchronizing
disk stores.
Always use -sync=false when starting multiple members
on the same machine, especially when executing sqlf commands
from a shell script or batch file, so that the script file does not hang
while waiting for a particular SQLFire member to start. You can use
the sqlf locator wait and/or sqlf server
wait later in the script to verify that each server has finished
synchronizing and has reached the "running" state. For example:
#!/bin/bash
# Start all local SQLFire members to
waiting state, regardless of which
member holds the most recent
# disk store files:
sqlf locator start -dir=/locator1
-sync=false
sqlf server start -client-port=1528
-locators=localhost[10334]
-dir=/server1 -sync=false
sqlf server start -client-port=1529
-locators=localhost[10334]
-dir=/server2 -sync=false
# Wait until all members have
finished synchronizing and starting:
sqlf locator wait -dir=/locator1
sqlf server wait -dir=/server1
sqlf server wait -dir=/server2
# Continue any additional tasks that
require access to the SQLFire
members...
[...]
The address to which this peer binds for receiving peer-to-peer
messages. By default sqlf uses the -peer-discovery-address value.
-bind-address
If true then it starts a network server (see the
-client-bind-address and -client-port
-run-netserver
options to specify where the server should listen) that can service
thin clients (defaults to true).
If set to false, then the -client-bind-address and
-client-port options have no affect. This option defaults
to true.
Address to which the network controller binds for client connections.
This takes effect only if -run-netserver option is not set
to false.
-client-bind-address
379
sqlf Launcher Commands