The
ccvsd
program processes on-line transactions, such as authorizations,
as you request them. You must run this in the background so that
these transactions are actually sent to the processor. If you
do not, the authorizations will never be performed.
You must specify the name of the configuration you wish to do processing
for. Also, if you used a non-default location for the configuration directory
(the location of the CCVS configuration files and transaction queues),
you must set the
CCVS_CONFIG_DIR
environment variable to point to it.
ccvsd
watches for transactions constantly. If you do an auth
or reverse,
ccvsd
should begin processing it immediately (within one second),
unless the modem is already in use.
You can check how many transactions
ccvsd
has pending by using the
cvcli
commands "list unauth" or "count unauth". The transactions that
ccvsd
will process are exactly those transactions in the "unauth" state.
When
ccvsd
has finished with them, those transactions will be in
one of the states "auth", "denied", or "review".
OPTIONS
-d
Cause
ccvsd
to behave like a more traditional BSD daemon.
It will put itself in the background,
it will create its own process group,
and it will avoid having a controlling TTY.
If you don't know whether you want these features, discuss this
information with your system administrator.
-V
Display the version of CCVS being used and then exit without
performing any work. (This does read the configuration file
to ensure that it exists and is valid.)
