flush_ctl usage is incorrect for persistence

Description From Perry Krug 2010-10-28 17:19:31 [reply] Private

The current usage reads:

Usage: /opt/membase/bin/ep_engine/management/flushctl_auth host:port evict key
or /opt/membase/bin/ep_engine/management/flushctl_auth host:port set param
value
or /opt/membase/bin/ep_engine/management/flushctl_auth host:port start
persistence
or /opt/membase/bin/ep_engine/management/flushctl_auth host:port stop
persistence

Available params:
min_data_age - minimum data age before flushing data"
queue_age_cap - maximum queue age before flushing data"
max_txn_size - maximum number of items in a flusher transaction
bg_fetch_delay - delay before executing a bg fetch (test feature)
max_size - max memory used by the server
mem_high_wat - high water mark
mem_low_wat - low water mark
==================

Notice the "start persistence" and "stop persistence". The word persistence
should be removed since it is not a valid argument and there should be a
description as to what "start" or "stop" actually does.