From: vda <vda@port.imtp.ilyichevsk.odessa.ua>
To: "Mr. James W. Laferriere" <babydr@baby-dragons.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Adding KERN_INFO to some printks
Date: Fri, 9 Nov 2001 21:17:00 +0000 [thread overview]
Message-ID: <01110921170000.00807@nemo> (raw)
In-Reply-To: <Pine.LNX.4.40.0111091200310.2020-100000@filesrv1.baby-dragons.com>
In-Reply-To: <Pine.LNX.4.40.0111091200310.2020-100000@filesrv1.baby-dragons.com>
On Friday 09 November 2001 17:02,
"Mr. James W. Laferriere" <babydr@baby-dragons.com> wrote:
> Hello Vda , Would you share your /etc/syslog.conf file ?
> I'd really like to see Good example of one . Most of the docs
> describe what all the options do , But don't show how they relate
> in the config file . Tia , JimL
>
> > I configured my syslog to sort all kernel msgs to
> > /var/log/syslog.N.debug|info|notice|warn|... (you got the idea)
> > and made it spew everything on tty12, and warnings only to tty11.
> >
> > I got tired of seeing purely informative messages on tty11 every
> > boot. They shouldn't be there.
# /etc/syslog.conf
#
# Message proirities:
# debug info notice warning err crit alert emerg
*.debug /var/log/syslog.7.debug
*.info /var/log/syslog.6.info
*.notice /var/log/syslog.5.notice
*.warn /var/log/syslog.4.warn
*.err /var/log/syslog.3.err
*.crit /var/log/syslog.2.crit
*.alert /var/log/syslog.1.alert
*.emerg /var/log/syslog.0.emerg
# >= crit: these will go to console too
# vda: had to comment it out: was dying on SAK 'coz held /dev/console open
# I hope syslogd maintainer will someday read this...
##*.crit /dev/console
# Log everything on 12th console, log 'serious' things on 11th
*.* /dev/tty12
*.warn /dev/tty11
#
# This might work instead to log on a remote host:
# *.* @hostname
next parent reply other threads:[~2001-11-09 19:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.40.0111091200310.2020-100000@filesrv1.baby-dragons.com>
2001-11-09 21:17 ` vda [this message]
2001-11-08 14:35 [PATCH] Adding KERN_INFO to some printks vda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01110921170000.00807@nemo \
--to=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=babydr@baby-dragons.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox