gws − Gigapxy web service daemon.
gws [−h?TvVqkU] [−C config_file] [−l logfile}] [−p pidfile]
gws is the front−end module of Gigapxy. It handles user and administrative requests submitted via HTTP protocol. The format of requests is described in the gigapxy(1) manpage.
gws dispatches user requests to Gigapxy engines, instances of a gng(1) daemon. At least one gng should be running for Gigapxy to accept requests for data. A gws can control up to 64 engines.
gws takes its parameters from a configuration file, which is either gws.conf or gigapxy.conf by default and can contain sections for any or all gigapxy modules. gws will look for the default configuration in a) current directory; b) /etc; c) /usr/local/etc. Path to a specific configuration file could be given at command−line (see OPTIONS). Configuration options for gws are described in detail in gws.conf(5) manpage.
gws rereads its configuration in response to SIGHUP. gws will force−rotate its log in response to SIGUSR1.
accepts the following options:
−h, −−help, −?, −−options
output brief option guide. This is NOT the behavior when run without parameters.
−C, −−config path
specify configuration file.
−l, −−logfile path
specify log file.
−p, −−pidfile path
specify pid file.
run as a terminal (non-daemon) application. This is the default behavior when gws is run by a non−privileged user. −T could be specified when run as root in order NOT to become a daemon, for instance, for debugging purposes.
set the level of verbosity in the output. This option could be repeated to get to the desired level, which is 0, unless the option is used at least once. Level 0 will reduce output to the very essential log entries of NRM (normal) priority; level 1 will set verbosity to output to INF (info): suitable for monitoring but not debugging; level 2 will enable DBG (debug) level for most (but not all) application modules; level 3 will set DBG (debug) for all modules. This switch has a rather inflexible nature, for more precise setting of log levels please use config settings alone.
output application’s version and quit.
send no output to terminal. This is to supress any output normally sent to standard output or error streams. Unless specified, when run from a non−privileged account, gws will mirror diagnostic messages sent to the log (as specified with the −l option) to standard output.
use legacy multicast API. gws uses newer protocol−agnostic API by default, some (older) systems may not fully support it or exhibit erroneous behavior when using it. Enabling this option will have gws use the older protocol−specific multicast API.
Disable authorization (if configured). This option allows a quick command−line override to disable whatever authorization method has been configured.
Pavel V. Cherenkov