TABLE OF CONTENTS
programs/rams-proxy [ Generics ]
NAME
rams-proxy - libram rpc based proxy
SYNOPSIS
rams-proxy [-V] [-h] [-v] [-s] [-x] [-b pid] [-o output] [-m modulepath] [-c connect] [-r rpcargs] backend
DESCRIPTION
rams-proxy can be used to build a proxy for libram. The clients are configure to use the libram-rpc(3) backend module to connect to a a rams-proxy on a (possible remote) machine. One can also connect multiple clients to one rams-proxy server to analyse data from more than one client.
rams-proxy itself does not do any analysis, but instead uses one of the libram-modules to do the analysis.
ARGUMENTS
- -V: print version info. Specifying more than one -V outputs more information.
- -h: print usage information
- -v: be verbose about the data processing
- -s: try to use libram synchronous mode. See libram-synchronous(3) and libram-asynchronous(3) for details about the synchronous modes of libram(3)
- -x: exit server loop if last client disconnects
- -b: daemonize and detach from terminal, write pid to pidfile
- -o: save output to file
- -m: specify the the path where modules are searched. If this option is omitted, the environment variable LIBRAM_MODULEPATH is used. If this is empty, the module path used at configure time is used.
- -c: the connect string for the backend module. The connect strings are documented in the manual page of the corresponding module.
- -r: the connect string for the rpcserver side component. See libramrpcserver_init(3) for details about the rpc server arguments.
- module: specifies which module should be used by rams-proxy.
ENVIRONMENT
- LIBRAM_MODULEDIR: directory of libram modules
SEE ALSO
libram(3), libram-rpc(3), libram-rpcserver(3)