reader.conf – configuration file for pcscd readers’ drivers Description The /etc/reader.conf.d/reader.conf file contains configuration information for serial and (some) PCMCIA smart card readers. USB readers SHALL NOT be configured using this file. pcscd uses another mechanism to automatically load USB drivers. Syntax The /etc/reader.conf.d/reader.conf is a regular text file. Each reader must be defined by…
reader.conf – configuration file for pcscd readers’ drivers Description The /etc/reader.conf.d/reader.conf file contains configuration information for serial and (some) PCMCIA smart card readers. USB readers SHALL NOT be configured using this file. pcscd uses another mechanism to automatically load USB drivers. Syntax The /etc/reader.conf.d/reader.conf is a regular text file. Each reader must be defined by…
rcsfile – RCS file format Description An RCS file’s contents are described by the grammar below. The text is free format: space, backspace, tab, newline, vertical tab, form feed, and carriage return (collectively, white space) have no significance except in strings. However, white space cannot appear within an id, num, or sym, and an RCS…
rcS – variables that affect the behavior of boot scripts Description The /etc/default/rcS file contains variable settings in POSIX format: VAR=VAL Only one assignment is allowed per line. Comments (starting with ‘#’) are also allowed. Options The following variables can be set. TMPTIME On boot the files in /tmp will be deleted if their modification…
"razor-whitelist" – Format for Vipul’s Razor Whitelist Description The razor whitelist is a list of email addresses and body signatures. Emails that match the whitelist are not processed by any of the Razor Agents. That is, They are not checked, reported, or revoked. In the case of razor-check(1), they are instantly marked as non-spam. Location…
Razor-Agents – Collection of files for checking, reporting, and revoking spam Description Vipul’s Razor is a distributed, collaborative, spam detection, reporting, and filtering network. The primary focus of the system is to identify and remove all email spam from the internet. Visit the website at http://razor.sourceforge.net/. Usage First a razorhome directory should be created where…
"razor-agent.conf" – Configuration file for Razor Agents Description "razor-agent.conf" is a configuration file read by the razor agents, which include razor-check(1), razor-admin(1), razor-report(1), and razor-revoke(1). The format is “attribute = value” pairs, one pair per line. Lines that begin with `#’ are treated as comments. Attributes Following attributes can be specified: razorhome Directory where Razor…
"razor-agent.conf" – Configuration file for Razor Agents Description "razor-agent.conf" is a configuration file read by the razor agents, which include razor-check(1), razor-admin(1), razor-report(1), and razor-revoke(1). The format is “attribute = value” pairs, one pair per line. Lines that begin with `#’ are treated as comments. Attributes Following attributes can be specified: razorhome Directory where Razor…
/etc/isdn/rate.conf – rate and provider configuration Description isdnlog and related programs like isdnrep or isdnrate obtain the information about telephone rates or fees from a rate-file. In addition to the general data from the rate-file it is necessary to provide information about the individual situation. This is the purpose of the configuration file rate.conf. Words…
/etc/isdn/rate.conf – rate and provider configuration Description isdnlog and related programs like isdnrep or isdnrate obtain the information about telephone rates or fees from a rate-file. In addition to the general data from the rate-file it is necessary to provide information about the individual situation. This is the purpose of the configuration file rate.conf. Words…
rate-files – Format of rate-files Description The rate-files used by isdnlog(8) and by isdnrate(1) are textfiles defining the telephone fees for different destinations at certain dates/times for all providers of one country. The rate-files have the following overall layout: Header entries Provider entries Comments starting with a hash-sign ‘#’ and empty lines are ignored. The…
NAME ras_palette – format descriptions for palette files for NCAR View SYNOPSIS palette_file.pal palette_file.txt DESCRIPTION NCAR View supports a binary as well as a textual format for color palettes. The binary format is compatible with NCSA HDF and must have a file extension of ".pal". The palette has a red, a green, and a blue…
ras_formats – Information on raster formats supported by NCAR Graphics and NCAR View. Synopsis Abekas A60, AVS, Generic Binary, HDF, HPPCL, NRIF, Sun, SGI, and XWD. Description NCAR Graphics and NCAR View applications are built upon a common library that provides read and write access to raster imagery. The table below summarizes the support that…
rarc – ra client resource file. Synopsis rarc Description Ra* clients will open this file if its in the users $HOME directory, or in the $ARGUSHOME directory, and parse it to set common configuration options. All of these values will be overriden by options set on the command line, or in the file specified using…
ranonymize.conf – ranonymize(1) configuration file. Synopsis ranonymize.conf Description This configuration file provides the ability to specify options for argus data anoymization. Options The anonymization clients have a small number of options for controlling specific aspects of the anonymization function and its output. Timestamps, Reference and Sequence Numbers Ranonymize anonymizes various fields in Argus records, such…
rancid.types.conf – rancid device type configuration file Description rancid.types.conf contains formatted configuration lines that define the device types that are available for use in the <device_type> field of the router.db(5) configuration file. The rancid.types.base configuration file follows the same format but defines the base types described in router.db(5). Users are STRONGLY discouraged from altering this…
rancid.types.conf – rancid device type configuration file Description rancid.types.conf contains formatted configuration lines that define the device types that are available for use in the <device_type> field of the router.db(5) configuration file. The rancid.types.base configuration file follows the same format but defines the base types described in router.db(5). Users are STRONGLY discouraged from altering this…
rancid.conf – rancid environment configuration file Description rancid.conf contains environment configuration information for rancid-run(1) and rancid-cvs(1), including shell PATH, list of rancid groups, etc. It is read by several scripts at run-time and others inherit the configration from a parent process which has read it. The syntax of rancid.conf is that of sh(1). rancid.conf is…
ralabel.conf – ralabel resource file. Synopsis ralabel.conf Description This configuration is a ralabel(1) configuration file. The concept is to provide a number of labeling strategies with configuration capabilities for each of the labelers. This allows the user to specify the order of the labeling, which is provided to support hierarchical labeling. Here is a valid…
radvd.conf – configuration file of the router advertisement daemon radvd Description This file describes the information which is included in the router advertisement (RA) of a specific interface. The file contains one or more interface definitions of the form: interface name { list of interface specific options list of prefix definitions list of clients (IPv6…