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
LOGGER(1)							   User Commands							 LOGGER(1)

NAME
logger - a shell command interface to the syslog(3) system log module SYNOPSIS
logger [options] [message] DESCRIPTION
logger makes entries in the system log. It provides a shell command interface to the syslog(3) system log module. OPTIONS
-n, --server server Write to the specified remote syslog server instead of to the builtin syslog routines. Unless --udp or --tcp is specified the log- ger will first try to use UDP, but if it fails a TCP connection is attempted. -d, --udp Use datagram (UDP) only. By default the connection is tried to syslog port defined in /etc/services, which is often 514. -T, --tcp Use stream (TCP) only. By default the connection is tried to syslog-conn port defined in /etc/services, which is often 601. -P, --port port Use the specified port. -i, --id Log the process ID of the logger process with each line. -f, --file file Log the contents of the specified file. This option cannot be combined with a command-line message. -h, --help Display a help text and exit. -p, --priority priority Enter the message into the log with the specified priority. The priority may be specified numerically or as a facility.level pair. For example, -p local3.info logs the message as informational in the local3 facility. The default is user.notice. -s, --stderr Output the message to standard error as well as to the system log. -t, --tag tag Mark every line to be logged with the specified tag. -u, --socket socket Write to the specified socket instead of to the builtin syslog routines. -V, --version Display version information and exit. -- End the argument list. This is to allow the message to start with a hyphen (-). message Write the message to log; if not specified, and the -f flag is not provided, standard input is logged. The logger utility exits 0 on success, and >0 if an error occurs. Valid facility names are: auth, authpriv (for security information of a sensitive nature), cron, daemon, ftp, kern (can't be generated from user process), lpr, mail, news, security (deprecated synonym for auth), syslog, user, uucp, and local0 to local7, inclusive. Valid level names are: alert, crit, debug, emerg, err, error (deprecated synonym for err), info, notice, panic (deprecated synonym for emerg), warning, warn (deprecated synonym for warning). For the priority order and intended purposes of these levels, see syslog(3). EXAMPLES
logger System rebooted logger -p local0.notice -t HOSTIDM -f /dev/idmc logger -n loghost.example.com System rebooted SEE ALSO
syslog(3), syslogd(8) STANDARDS
The logger command is expected to be IEEE Std 1003.2 ("POSIX.2") compatible. AVAILABILITY
The logger command is part of the util-linux package and is available from Linux Kernel Archive <ftp://ftp.kernel.org/pub/linux/utils/util- linux/>. util-linux April 2013 LOGGER(1)
All times are GMT -4. The time now is 04:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy