Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

roundup-server(1) [debian man page]

ROUNDUP-SERVER(1)					      General Commands Manual						 ROUNDUP-SERVER(1)

NAME
roundup-server - start roundup web server SYNOPSIS
roundup-server [options] [name=tracker home]* OPTIONS
-C file Use options read from the configuration file (see below). -n hostname Sets the host name in the Roundup web server interface. -p port Sets the port to listen on (default: 8080). -d file Daemonize, and write the server's PID to the nominated file. -l file Sets a filename to log to (instead of stdout). This is required if the -d option is used. -i file Sets a filename to use as a template for generating the tracker index page. The variable "trackers" is available to the template and is a dict of all configured trackers. -s Enables to use of SSL. -e file Sets a filename containing the PEM file to use for SSL. If left blank, a temporary self-signed certificate will be used. -N Log client machine names instead of IP addresses (much slower). -u UID Runs the Roundup web server as this UID. -g GID Runs the Roundup web server as this GID. -d PIDfile Run the server in the background and write the server's PID to the file indicated by PIDfile. The -l option must be specified if -d is used. -v Print version and exit. -h Print help and exit. name=tracker home Sets the tracker home(s) to use. The name variable is how the tracker is identified in the URL (it's the first part of the URL path). The tracker home variable is the directory that was identified when you did "roundup-admin init". You may specify any number of these name=home pairs on the command-line. For convenience, you may edit the TRACKER_HOMES variable in the roundup-server file instead. Make sure the name part doesn't include any url-unsafe characters like spaces, as these confuse the cookie handling in browsers like IE. EXAMPLES
roundup-server -p 9000 bugs=/var/tracker reqs=/home/roundup/group1 Start the server on port 9000 serving two trackers; one under /bugs and one under /reqs. CONFIGURATION FILE
See the "admin_guide" in the Roundup "doc" directory. AUTHOR
This manpage was written by Bastian Kleineidam <calvin@debian.org> for the Debian distribution of roundup. The main author of roundup is Richard Jones <richard@users.sourceforge.net>. 27 July 2004 ROUNDUP-SERVER(1)

Check Out this Related Man Page

muroarstream(1) 					System User's Manual: muroarstream					   muroarstream(1)

NAME
muroarstream - Simple RoarAudio client SYNOPSIS
muroarstream [OPTIONS] DESCRIPTION
muroarstream is a simple client for the RoarAudio sound system. It is based on muRoar (libmuroar). It can only be used to send data to or get data from the server. No control functionality is supported. OPTIONS
--help Display a brief help. -f --file FILE Sets the file to read from or write to. --server SERVER Sets the server to SERVER. Default is to auto detect the server. (see below) -R --rate RATE Sets the sample rate. This defaults to 44100Hz. -C --channels CHANS Sets the number of channels. this defaults to 2 channels (stereo). Symbolic names "mono" and "stereo" as well as "default" can be used. -B --bits BITS Sets the number of bits per sample. The default is 16bit per sample. -E --codec CODEC Sets the codec to use. The default depends on used subsystem. For Waveform it uses Signed native PCM, for Light DMX512 and for MIDI MIDI. The following symbolic names can be used: default, pcm, pcm_s, pcm_u, ogg_vorbis, vorbis, alaw, mulaw, ulaw, dmx512, roardmx, midi. --play Use Playback mode (send data to the server). This is the default. --monitor Use monitor mode (get a copy of the played data from the server). --wave Use Waveform subsystem (default). --midi Use MIDI subsystem. --light Use Light Control subsystem. AUTO DETECTION
The server will be auto located if no server name is given. First it will look for the environment variable $ROAR_SERVER. If this vari- able is non existing libmuroar will do the auto location based on a list of possible server locations. This list contains the global UNIX socket address, the user's private socket address and an entry for localhost using TCP/IP. The UNIX socket addresses are only compiled in if UNIX socket support is detected. SEE ALSO
roarcat(1), RoarAudio(7). muRoar 22 February 2010 muroarstream(1)
Man Page