01-14-2016
According to the
Solaris syslog.conf man page, you need tabs (not spaces) between the message classes and the destination for syslog messages of those classes. Furthermore, the examples and description talk about host names; not IP addresses.
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. 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
3. 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
4. UNIX for Dummies Questions & Answers
Hi,
We had a hardware problem at work and none of the kernel problems outputted to the log file, just the screen. How can I configure the syslogd.conf file to record kernel events (ie hardware problems) to /dev/console and/var/log/messages. Can I just put:
/dev/console /var/log/messages on... (5 Replies)
Discussion started by: mojoman
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. BSD
I'm trying to get all ipfw logs going to ipfw.log I've managed that, but ipfw.log is also getting stuff that shows up in system.log
!-ipfw
*.notice;authpriv,remoteauth,ftp,install,internal.none /var/log/system.log
kern.* /var/log/kernel.log... (5 Replies)
Discussion started by: jnojr
5 Replies
LEARN ABOUT LINUX
warn.conf
warn.conf(4) File Formats warn.conf(4)
NAME
warn.conf - Kerberos warning configuration file
SYNOPSIS
/etc/krb5/warn.conf
DESCRIPTION
The warn.conf file contains configuration information specifying how users will be warned by the ktkt_warnd daemon about ticket expiration
on a Kerberos client. Credential expiration warnings are sent, by means of syslog, to auth.notice. All other warning messages are sent to
daemon.notice.
Each Kerberos client host must have a warn.conf file in order for users on that host to get Kerberos warnings from the client. Entries in
the warn.conf file must have the following format:
principal syslog | terminal | mail time [email_address]
principal Specifies the principal name to be warned. The asterisk (*) wildcard can be used to specify groups of principals.
syslog Sends the warnings to the system's syslog. Depending on the /etc/syslog.conf file, syslog entries are written to the
/var/adm/messages file and/or displayed on the terminal.
terminal Sends the warnings to display on the terminal.
mail Sends the warnings as email to the address specified by email_address.
time Specifies how much time before the TGT expires when a warning should be sent. The default time value is seconds, but you
can specify h (hours) and m (minutes) after the number to specify other time values.
email_address Specifies the email address at which to send the warnings. This field must be specified only with the mail field.
EXAMPLES
Example 1: Specifying warnings
The following warn.conf entry
* syslog 5m
specifies that warnings will be sent to the syslog five minutes before the expiration of the TGT for all principals. The form of the mes-
sage is:
jdb@ACME.COM: your kerberos credentials expire in 5 minutes
FILES
/usr/lib/krb5/ktkt_warnd Kerberos warning daemon
SEE ALSO
ktkt_warnd(1M), syslog.conf(4), SEAM(5)
SunOS 5.10 22 Apr 2003 warn.conf(4)