mmpongd(6) [debian man page]
MMPONGD(6) Games Manual MMPONGD(6) NAME
mmpongd - masssively multiplayer pong daemon SYNOPSIS
mmpongd [--model=%s] [--paddles=%s] [--address=%s] [--port=%d] [--dev=%s] [--background] [--nthreads=%d] [--max-connect=%d] [--max-per- ip=%d] [--max-payload=%d] [--min-rttm-interval=%s] [--client-timeout=%d] [--verbose] [--help] [--version] DESCRIPTION
This manual page documents briefly the mmpongd command. mmpongd is the server for the massive multiplayer pong ( mmpong ) game. It is capable of serving hundreds of clients simultaneously and scales sufficiently well on SMP machines (pthreads). OPTIONS
-m, --model=%s Game model to play (defaults to "linear") -r, --paddles=%s Paddle profile to be used by all teams (defaults to "flat") -a, --address=%s Local hostname or IP address to bind to -p, --port=%d Local port to listen on -d, --dev=%s Network device to bind the socket to -b, --background Daemonize and return -n, --nthreads=%d Number of threads to run simultaneously (-1 == auto) -c, --max-connect=%d Maximum number of clients to serve simultaneously (-1 == unlimited) -i, --max-per-ip=%d Maximum number of clients to allow to connect from one host (-1 == unlimited) -l, --max-payload=%d Restrict traffic to specified amount of kBytes/sec (-1 == unlimited) -s, --min-rttm-interval=%s Minimal interval between near-synchronous packet transfers (-1 == unrestricted) -t, --client-timeout=%d Timeout between status updates before client session is terminated, measured in msecs (-1 == no timeout) --verbose Log more messages to the console --help Show help screen --version Show version information SEE ALSO
mmpong-gl(6), mmpong-caca(6). AUTHOR
mmpongd was written by: Kai Hertel, Andre Gaul This manual page was written by Andre Gaul <gaul@web-yard.de>. January 12, 2009 MMPONGD(6)
Check Out this Related Man Page
KUMO-SERVER(1) General Commands Manual KUMO-SERVER(1) NAME
kumo-server - kumofs server daemon SYNOPSIS
kumo-server -m <addr[:port=19700]> -p <addr[:port19700]> -l <addr[:port=19800]> -s <path.tch> DESCRIPTION
kumo-server stores actual data. You can add kumo-servers after buiding the cluster. You can get live status of the kumo-manager using kumostat and kumotop command. OPTIONS
-l <addr[:port=19800]> --listen listen address -L <port=19900> --stream-listen listen port for replacing stream -f <dir=/tmp> --offer-tmp path to temporary directory for replacing -s <path.tch> --store path to database -m <addr[:port=19700]> --manager1 address of manager 1 -p <addr[:port=19700]> --manager2 address of manager 2 -S <number=20> --replicate-set-retry replicate set retry limit -D <number=20> --replicate-delete-retry replicate delete retry limit -gN <seconds=60> --garbage-min-time minimum time to maintenance deleted key -gX <seconds=3600> --garbage-max-time maximum time to maintenance deleted key -gS <kilobytes=2048> --garbage-mem-limit maximum memory usage to memory deleted key -k <number=2> --keepalive-interval keepalive interval in seconds -Ys <number=1> --connect-timeout connect timeout time in seconds -Yn <number=4> --connect-retry-limit connect retry limit -Ci <number=8> --clock-interval clock interval in seconds -TW <number=2> --write-threads number of threads for asynchronous writing -TR <number=4> --read-threads number of threads for asynchronous reading -o <path.log> --log output logs to the file -g <path.mpac> --binary-log enable binary log -v --verbose -d <path.pid> --daemon EXAMPLE
[on svr1 ]$ kumo-server -v -l svr1 -m mgr1 -p mgr2 -s /var/kumodb.tch -gN 5 -gS 20480 [on svr2 ]$ kumo-server -v -l svr2 -m mgr1 -p mgr2 -s /var/kumodb.tch -TR 6 -TW 4 [on svr3 ]$ kumo-server -v -l svr3 -m mgr1 -p mgr2 -s /var/kumodb.tch -Ci 16 [localhost]$ kumo-server -v -m localhost -l localhost:19801 -L 19901 -s ./database1.tch [localhost]$ kumo-server -v -m localhost -l localhost:19802 -L 19902 -s ./database2.tch [localhost]$ kumo-server -v -m localhost -l localhost:19803 -L 19902 -s ./database3.tch SEE ALSO
kumostat(1), kumotop(1), kumolog(1), kumomergedb(1), kumohash(1). kumo-server July 2009 KUMO-SERVER(1)