-->

Previous | Table of Contents | Next

Page 1186

BUGS

There is a maximum of 35 aliases, due to the way the getservent(3) code is written.

Lines longer than BUFSIZ (currently 1024) characters will be ignored by getservent(3), getservbyname(3), and getservbyport(3). However, this will also cause the next line to be misparsed.

FILES


/etc/services            The Internet network services list

/usr/include/netdb.h     Definition of _PATH_SERVICES

SEE ALSO


getservent(3), getservbyname(3), getservbyport(3),

setservent(3), endservent(3), protocols(5), listen(2),

inetd.conf(5), inetd(8), Assigned Numbers RFC, most recently RFC 1700 (AKA STD0002),

Guide to Yellow Pages Service, Guide to 

BIND/Hesiod Service.

Linux, 11 January 1996

shells

shells—Pathnames of valid login shells.

DESCRIPTION

/etc/shells is a text file that contains the full pathnames of valid login shells. This file is consulted by chsh(1) and is available to be queried by other programs.

EXAMPLES

/etc/shells may contain the following paths:


/bin/sh

/bin/csh

FILES


/etc/shells

SEE ALSO

chsh(1)

21 November 1993

syslog.conf

syslog.conf—syslogd(8) configuration file.

DESCRIPTION

The syslog.conf file is the configuration file for the syslogd(8) program. It consists of lines with two fields: the selector field, which specifies the types of messages and priorities to which the line applies, and an action field, which specifies the action to be taken if a message syslogd received matches the selection criteria. There cannot be any spaces in the action field. The selector field is separated from the action field by one or more tab or space characters. (This is a departure from the standard BSD way of doing things; both tabs and spaces can be used to separate the selector from the action.)

The selector functions are encoded as a facility, a period (.), and a level, with no intervening whitespace. Both the facility and the level are case insensitive.

Page 1187

The facility describes the part of the system generating the message and is one of the following keywords: auth, authpriv, cron, daemon, kern, lpr, mail, mark, news, syslog, user, uucp, and local0 through local7. These keywords (with the exception of mark) correspond to the similar Dv LOG_ values specified to the openlog(3) and syslog(3) library routines.

The level describes the severity of the message and is a keyword, optionally preceded by an equals (=), from the following ordered list (higher to lower): emerg, alert, crit, err, warning, notice, info, and debug. These keywords correspond to the similar Dv LOG_ values specified to the syslog library routine.

See syslog(3) for further descriptions of both the facility and level keywords and their significance.

If a received message matches the specified facility and is of the specified level (or a higher level if level was specified without =), the action specified in the action field will be taken.

Multiple selectors may be specified for a single action by separating them with semicolon (;) characters. It is important to note, however, that each selector can modify the ones preceding it.

Multiple facilities may be specified for a single level by separating them with comma (,) characters.

An asterisk (*) can be used to specify all facilities or all levels.

The special facility "mark" receives a message at priority "info" every 20 minutes (see syslogd(8)). This is not enabled by a facility field containing an asterisk.

The special level "none" disables a particular facility.

The action field of each line specifies the action to be taken when the selector field selects a message. There are four forms:

A pathname (beginning with a leading slash). Selected messages are appended to the file.

A hostname (preceded by an at (@) sign). Selected messages are forwarded to the syslogd program on the named host.

A comma-separated list of users. Selected messages are written to those users if they are logged in.

An asterisk. Selected messages are written to all logged-in users.

Blank lines and lines whose first non-blank character is a hash (#) character are ignored.

EXAMPLES

A configuration file might appear as follows:


# Log all kernel messages, authentication messages of

# level notice or higher and anything of level err or

# higher to the console.

# Don't log private authentication messages!

*.err;kern.*;auth.notice;authpriv.none                   /dev/console



# Log anything (except mail) of level info or higher.

# Don't log private authentication messages!

*.info;mail.none;authpriv.none                          /var/log/messages



# Log debug messages only

*.=debug                                                /var/log/debug



# The authpriv file has restricted access.

authpriv.*                                              /var/log/secure



# Log all the mail messages in one place.

mail.*                                                  /var/log/maillog



# Everybody gets emergency messages, plus log them on another

# machine.

*.emerg                                                 *

*.emerg                                                 @arpa.berkeley.edu



Previous | Table of Contents | Next