NAME

rc_server - RCDS Server

SYNOPSIS

rc_server -af authority-file [ -create ] [ -logfile filename ] [ -nosyslog ] [ -syslog ] -uf user-file

DESCRIPTION

      rc_server maintains a database of resource metadata, indexed by the Uniform Resource Identifier (URI) of the resource. rc_server understands three types of resource metadata: assertions, locations, and certificates. Assertions associate an attribute value with an attribute name. Locations associate zero or more Uniform Resource Locators (URLs), each indicating the location of a particular form of a resource, with a stable name for that resource. A certificate is a digital signature on an ordered list of one or more assertions.

      For the most part, the metadata is opaque to rc_server itself, the purpose of the server being to provide storage and retrieval of the metadata to authorized and interested parties.

OPTIONS



-af authority-file
The authority file defines the list of domains for which the server is authoritative. Eventually, queries for URIs in other domains may result in redirects being returned to the client; updates to URIs in other domains will be refused. In the current version of rc_server,the information in the authority file is not used. However, if the -af option is used, the authority_file must exist and be in the proper format.
Each line of the authority file is expected to be in the following format:
uri-domain:server-domain
where uri-domain is the domain that appears in a URI, and server-domain is the domain name of an RC server that is authoritative for that URI-domain.

-create
Create database if it doesn't already exist. If this option is omitted and the database does not exist, rc_server will print an error message and exit.

-logfile filename
Log debugging information to filename.

-nosyslog
Do not log information using syslog(3).

-syslog
Log debugging information using syslog(3).This is not exclusive with -logfile;logs can be sent to both syslog and a log file.

-uf user-file
The user file defines a list of authorized users. Only users listed in this file may write to the database. Each line of the file is in the following format:
username:user-id:permissions:authtype:secret
where username is some identifier for the user (not necessarily a UNIX login id); user-id is a unique integer assigned to that user; permissions is a comma-separated list of permissions, taken from the list debug,lifn,url,urn,and revoke;authtype is the type of authentication used (currently only md5 is supported); and secret is a shared secret used for authentication. Secrets are random bit-strings encoded as short English words, and are generated by authbits(1).

SIGNALS

      rc_server recognizes the following signals:

SIGHUP
re-read configuration files.
SIGUSR1
increment debugging level.
SIGUSR2
set debugging level to 0.

      Most other ``fatal'' signals will cause rc_server to clean up and exit.

FILES

rc_server uses, and optionally creates, its database in the current directory. The names and formats of the files used vary depending on which back-end rc_server was compiled with.

SEE ALSO

sonard(1),rcdspp(1).

BUGS

This is still a prototype.