Sponsored Content
Operating Systems Solaris Solaris syslog messages cluttering screen Post 302878837 by admin_xor on Monday 9th of December 2013 07:39:31 AM
Old 12-09-2013
Wrench Solaris syslog messages cluttering screen

Well, this kind of silly but I think I am missing something. So we have this Solaris 10 server which acts as syslog server for network devices. Problem is the syslogs clutters whenever I use the
Code:
screen

utility for any work.

I am posting the conetent of
Code:
/etc/syslog.conf

Code:
# more /etc/syslog.conf
#ident  "@(#)syslog.conf        1.5     98/12/14 SMI"   /* SunOS 5.0 */
#
# Copyright (c) 1991-1998 by Sun Microsystems, Inc.
# All rights reserved.
#
# syslog configuration file.
#
# This file is processed by m4 so be careful to quote (`') names
# that match m4 reserved words.  Also, within ifdef's, arguments
# containing commas must be quoted.
#
*.err;kern.notice;auth.notice                   /dev/sysmsg
*.err;kern.debug;daemon.notice;mail.crit        /var/adm/messages

*.alert;kern.err;daemon.err                     operator
*.alert                                         root

*.emerg                                         *

# if a non-loghost machine chooses to have authentication messages
# sent to the loghost machine, un-comment out the following line:
#auth.notice                    ifdef(`LOGHOST', /var/log/authlog, @loghost)

mail.debug                      ifdef(`LOGHOST', /var/log/syslog, @loghost)

#
# non-loghost machines will use the following lines to cause "user"
# log messages to be logged locally.
#
ifdef(`LOGHOST', ,
user.err                                        /dev/sysmsg
user.err                                        /var/adm/messages
user.alert                                      `root, operator'
user.emerg                                      *
)
daemon.debug                    /var/log/connlog
auth.info                       /var/log/authlog
# filter for network devices 
local7.info;local7.notice;local7.warn;local7.error              /var/log/syslog_info
#BEGIN 
local0.emerg;local0.alert;local0.crit;local0.err;local0.warning;local0.notice;local0.info;local0.debug  /opt/app/data/dblog/dbeng.log
#END

Am I missing something in the config?
 

10 More Discussions You Might Find Interesting

1. Solaris

Solaris 9 login Screen not loading

The system loads fine no errors on the system during boot. when it tries to start it goes to hostname % it does not show the login screen for the users. any help on this would be great. is the X11 not starting properly? (16 Replies)
Discussion started by: deaconf19
16 Replies

2. Solaris

Jumpstart Solaris Installation Program screen

Hi! I'm trying to skip the installation welcome screen (actually the first three screens: The Solaris Installation Program screen, Identify This System screen and date and time settings - not timezone settings). Everything else runs automaticly from jumpstart except these three screens, just... (6 Replies)
Discussion started by: Luka
6 Replies

3. Solaris

solaris equivalent to the linux screen command

hi there is there a solaris equivalent to the linux screen command? (1 Reply)
Discussion started by: milhan
1 Replies

4. Solaris

Solaris Login Screen Not Loading

I (think I) successfully installed Solaris 10 5/09 on the IDE hard drive of my computer using the 5 installation CDs I downloaded from the Sun website. But now when I boot from the IDE hard drive I think it boots successfully but It asks me for the root password or Ctrl+D to abort. When I give it... (5 Replies)
Discussion started by: Bradj47
5 Replies

5. Shell Programming and Scripting

printing messages on the screen when background process is going on!

hello all, In my script i have written some messages which should come in screen while some background process is going on.. Like for example: if i want to add 2 numbers a and b ...when the addition is going on in the background i should get "ADDING TWO NUMBERS>>PLEASE WAIT " message on... (3 Replies)
Discussion started by: smarty86
3 Replies

6. Solaris

Solaris 10 screen capture

We are using Solaris 10 for our Radiation Treatment Planning and need to create a simulation for our service engineers. I need a screen capture tool that can not only capture screens, but create movies of mouse movements (similar to Captivate). I have contacted Oracle and talked to several people... (2 Replies)
Discussion started by: TomH
2 Replies

7. Shell Programming and Scripting

Script that prints 2 messages to a screen session

Im trying to make a script that prints 2 messages to a screen session, one after the other. screen -x session44 -X stuff "`printf "Test 1\r"`" This works fine, but adding a second lien with a different message yields no results. Changed Subject: Please Follow Forum Rules Regarding... (1 Reply)
Discussion started by: kylecn
1 Replies

8. Solaris

Login Screen in Solaris 11

I have a requirement to add a warning banner to the Solaris 11 login screen. Adding the banner was pretty easy in Solaris 10 by changing *Dtlogin. Does anyone know how to make the change in Solaris !!? (3 Replies)
Discussion started by: goose25
3 Replies

9. Solaris

Solaris 8, you boot the system but does not have anything on the screen (not started)

Greetings to all. I have two computers, Sun Blade 150. the first, had the Solaris 8 system, and that system needed to clone the "second" to start it with the same settings. Use a program to clone the drive, and then have cloned, had the error: Can't read disk label. Can't open disk... (4 Replies)
Discussion started by: feliz-58
4 Replies

10. Solaris

Dual screen in Solaris 10

Hi. I have a question.. how can i do a dual screen in CME with the same desktop.. with consule.. ?! sry for wrong selection in forum. (1 Reply)
Discussion started by: defs
1 Replies
syslog.conf(4)						     Kernel Interfaces Manual						    syslog.conf(4)

NAME
syslog.conf - syslogd configuration file SYNOPSIS
facility.severity destination Where: Is part of the system generating the message, specified in /usr/include/sys/syslog_pri.h. See also the syslogd(8) reference page. The severity level, which can be emerg, alert, crit, err, warning, notice, info, or debug. See /usr/include/sys/syslog_pri.h. The syslogd daemon logs all messages of the specified severity level plus all messages of greater severity. For example, if you specify level err, all messages of levels err, crit, alert, and emerg or panic are logged. A local file pathname to a log file, a host name for remote logging or a list of users. In the latter case the users will receive messages when they are logged in. An asterisk (*) causes a message to be sent to all users who are currently logged in. DESCRIPTION
The /etc/syslog.conf file is a system file that enables you to configure or filter events that are to be logged by syslogd. You can specify more than one facility and its severity level by separating them with semicolons. You can specify more than one facility logs to the same file by separating the facilities with commas, as shown in the EXAMPLES section. The syslogd daemon ignores blank lines and lines that begin with an octothorpe (#). You can specify # as the first character in a line to include comments in the file or to disable an entry. The facility and severity level are separated from the destination by one or more tab characters. If you want the syslogd daemon to use a configuration file other than the default, you must specify the file name with the following com- mand: # syslogd -f config_file Daily Log Files You can specify in the /etc/syslog.conf file that the syslogd daemon create daily log files. To create daily log files, use the following syntax to specify the path name of the message destination: /var/adm/syslog.dated/ { file} The file variable specifies the name of the log file, for example, mail.log or kern.log. If you specify a /var/adm/syslog.dated/file path name destination, each day the syslogd daemon creates a sub-directory under the /var/adm/syslog.dated directory and a log file in the sub-directory, using the following syntax: /var/adm/syslog.dated/ date / file Where: The date variable specifies the day, month, and time that the log file was created. The file variable specifies the name of the log file you previously specified in the /etc/syslog.conf file. The syslogd daemon automatically cre- ates a new date directory every 24 hours and also when you boot the system. The current directory is a link to the latest date directory. To get the latest logs, you only need to reference the /var/adm/syslog.dated/current directory. EXAMPLES
The following is a sample /etc/syslog.conf file: # # syslogd config file # # facilities: kern user mail daemon auth syslog lpr binary # priorities: emerg alert crit err warning notice info debug # kern.debug /var/adm/syslog.dated/kern.log user.debug /var/adm/sys- log.dated/user.log daemon.debug /var/adm/syslog.dated/daemon.log auth.crit;syslog.debug /var/adm/syslog.dated/syslog.log mail,lpr.debug /var/adm/syslog.dated/misc.log msgbuf.err /var/adm/crash.dated/msgbuf.savecore kern.debug /var/adm/messages kern.debug /dev/console *.emerg * FILES
/etc/syslog.conf /etc/syslog.auth - Authorization file for remote logging. /usr/include/sys/syslog_pri.h - Common components of a syslog event log record. RELATED INFORMATION
Commands: /usr/sbin/syslogd(8), /usr/sbin/binlogd(8) System Administration delim off syslog.conf(4)
All times are GMT -4. The time now is 07:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy