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

NETDUMP-SERVER(8)						  System Programs						 NETDUMP-SERVER(8)

NAME
netdump-server - handle crash dumps over the network SYNOPSIS
netdump-server [--port portnumber] [--concurrent number] [--pidfile path] [--daemon] [--help] [--usage] DESCRIPTION
Listens to the network for clients that crashes and uses the netdump protocol to recieve a memory dump and a stack trace. The memory dump and oops message are stored in a timestamped directory in /var/crash. The server can also run scripts when some events happen. OPTIONS
--port portnumber Specifies the IP port number for the netdump server to listen to. The default is 6666. --concurrent number You can limit the amount of concurrent dumps being done at any one time. If more clients than the specified maximum connects at one time the last ones will just be logged and then rebooted. --pidfile path Store a pidfile. The default service uses /var/run/ttywatch.pid. The default is not to write a pidfile. --daemon ttywatch should background itself and run as a daemon. EXAMPLES
netdump-server --daemon This launches the netdump-server and puts it in the background, listening for crashed clients. EXIT STATUS
Exit status is 0 for a clean exit and non-0 for a non-clean exit. FILES
/etc/netdump.conf A configuration file read by netdump-server on startup. It is a "key=value" style file. Currently it supports the options: port, max_concurrent_dumps, daemon and pidfile. /etc/init.d/netdump-server An init script to start a default system installation of netdump-server. This is normally turned off by default; use the command /sbin/chkconfig netdump-server on to enable the netdump-server service. /var/crash The main directory where the crash dump files are stored. Each dump is put in a subdirectory named with the ip of the crashed machine and the date and time of the crash. /var/crash/scripts This directory can contain scripts that are run at various times. They all get passed the ip of the crashing machine as the first argument, and each one except netdump-start gets the directory that the dump is written into as the second argument. netdump-start - This is called when a client connects to the server to tell it that it has just started the netdump client. This normally means that the machine just booted up. netdump-crash - This is run when a client reports that it has crashed. If it returns a non-zero value the dump request will be ignored and the client will be told to reboot immediately netdump-nospace - This is run when there is not enough diskspace for the dump of the crashed machine. If this script exits with a non-zero return value netdump-server will try once again (but only once) before giving up the dump. If this script exits with a zero return value, netdump-server will reboot the client without performing a dump. netdump-reboot - This is run when netdump-server is finished with a client and is about to tell the client to reboot itself. SEE ALSO
netdump(8) BUGS
Report any bugs you find to http://bugzilla.redhat.com/bugzilla AUTHOR
Alexander Larsson <alexl@redhat.com> Linux 14 Feb 2002 NETDUMP-SERVER(8)
Man Page