12-11-2001
As I recall, telnetd and in.telnetd (your example) uses
/bin/login to manage user logins. There is a configuration file for /bin/login called
login.defs :
Quote:
NAME
/etc/login.defs - Login configuration
DESCRIPTION
The /etc/login.defs file defines the site-specific config-
uration for the shadow login suite. This file is
required. Absence of this file will not prevent system
operation, but will probably result in undesirable opera-
tion.
This file is a readable text file, each line of the file
describing one configuration parameter. The lines consist
of a configuration name and value, seperated by whites-
pace. Blank lines and comment lines are ignored. Com-
ments are introduced with a `#' pound sign and the pound
sign must be the first non-white character of the line.
Parameter values may be of four types: strings, booleans,
numbers, and long numbers. A string is comprised of any
printable characters. A boolean should be either the
and in the man page, the configuration for the logging behavior of
/bin/login is configured (just a few examples):
Quote:
FAILLOG_ENAB (boolean)
If yes then login failures will be accumulated in
/var/log/faillog in a faillog(8) format.
FAIL_DELAY (number)
Delay time in seconds after each failed login
attempt.
Does this help, or were you looking for more generic syslog.conf information not related to login and telnetd?
10 More Discussions You Might Find Interesting
1. Red Hat
Hi all
I have a RedHat Linux AS2.1 server that keep crashing/rebooting and there are no messages in the /var/log/messages file pointing to any problems. I had a look at the /etc/syslog.conf file to see what gets logged to /var/log/messages, but I don't know what else to add. Can anyone tell me... (1 Reply)
Discussion started by: soliberus
1 Replies
2. HP-UX
Hi I received this mail (root) on my hp-ux 11.00.
>------------ Event Monitoring Service Event Notification ------------<
Notification Time: Thu Mar 22 08:41:28 2007
hostname sent Event Monitor notification information:
/storage/events/disks/default/0_0_1_1.0.0 is >= 3.
Its current value... (6 Replies)
Discussion started by: touny
6 Replies
3. Linux
Hi everybody,
i have a little problem...
I have two server srv01 and srv02.
srv02 have a syslogd server onboard and listen on 515... not on 514 (it's busy).
How i configure the syslog.conf of srv01 for send logs on srv02:515 ???
Now i have on srv01:
*.* @srv02
if i write:
*.* ... (0 Replies)
Discussion started by: Zio Bill
0 Replies
4. Solaris
Has anyone here configured a central syslog server using syslog-ng ?
I have set one up and I'm trying to tune the syslog-ng.conf file, both for the server and the client. I have found lots of linux example files, but not much on Solaris which is slightly different.
So if you have a Solaris... (5 Replies)
Discussion started by: Tornado
5 Replies
5. Solaris
Hi Everyone,
I just wanted to know about the below entry in syslog.conf in Solaris 10:
kern.notice @destserver
Now the log will be redirected to destserver. But I want to know the location on the destserver where this log will be thrown.
Thanks in Advance,
Deepak (4 Replies)
Discussion started by: naw_deepak
4 Replies
6. UNIX for Advanced & Expert Users
I have a RHEL box that I want to be the loghost for all of the other systems on my network and have set up a /logs partitions to hold all of the logs. I've also created a file called current.log that will contain daily logs and created it using the following command: cp /dev/null current.log. ... (4 Replies)
Discussion started by: goose25
4 Replies
7. Shell Programming and Scripting
How can i configure messages with warn priority to be logged in /var/log/mywarnings.log ? (1 Reply)
Discussion started by: g0dlik3
1 Replies
8. Solaris
I would like to configure the syslog.conf to have a good monitoring information about my system.
do you have any idea about best configuration from your experience in your Data Centers
BR, (5 Replies)
Discussion started by: maxim42
5 Replies
9. Red Hat
Hi,
I would like to configure syslog linux client, syslog server is windows server.
so adding on linux client in /etc/syslog.conf @hostname will work in the place of directory location.
example of /etc/syslog.conf
# Log all kernel messages to the console.
# Logging much else clutters up... (2 Replies)
Discussion started by: manoj.solaris
2 Replies
10. Solaris
Hi Community
Which are the available entries to forward syslog in syslog.conf
i have put
*.err;kern.debug;daemon.notice;mail.crit;user.alert;user.emerg;kern.notice;auth.notice;kern.warning @172.16.200.50
and it's not going through.giving error message like below:
syslogd:... (2 Replies)
Discussion started by: bentech4u
2 Replies
LEARN ABOUT OPENDARWIN
syslog.conf
SYSLOG.CONF(5) BSD File Formats Manual SYSLOG.CONF(5)
NAME
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 receives matches the selection criteria. The selector field is separated from the action field by one or more tab charac-
ters.
The Selectors function are encoded as a facility, a period (``.''), and a level, with no intervening white-space. Both the facility and the
level are case insensitive.
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 ``LOG_'' values specified to the openlog(3) and syslog(3) library routines.
The level describes the severity of the message, and is a keyword from the following ordered list (higher to lower): emerg, alert, crit, err,
warning, notice, info and debug. These keywords correspond to the similar (LOG_) values specified to the syslog library routine.
See syslog(3) for a 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), 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, how-
ever, 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:
o A pathname (beginning with a leading slash). Selected messages are appended to the file.
o A hostname (preceded by an at (``@'') sign). Selected messages are forwarded to the syslogd program on the named host.
o A comma separated list of users. Selected messages are written to those users if they are logged in.
o 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
# 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
# Root and Eric get alert and higher messages.
*.alert root,eric
# Save mail and news errors of level err and higher in a
# special file.
uucp,news.crit /var/log/spoolerr
FILES
/etc/syslog.conf The syslogd(8) configuration file.
BUGS
The effects of multiple selectors are sometimes not intuitive. For example ``mail.crit,*.err'' will select ``mail'' facility messages at the
level of ``err'' or higher, not at the level of ``crit'' or higher.
SEE ALSO
syslog(3), syslogd(8)
HISTORY
The syslog.conf file appeared in 4.3BSD, along with syslogd(8).
BSD
June 9, 1993 BSD