All of lore.kernel.org
 help / color / mirror / Atom feed
From: j.neuschaefer@gmx.net (Jonathan Neuschäfer)
To: kernelnewbies@lists.kernelnewbies.org
Subject: how to configure printk() in 2.6 kernel
Date: Tue, 30 Aug 2011 21:25:13 +0200	[thread overview]
Message-ID: <20110830192513.GB1732@debian.debian> (raw)
In-Reply-To: <CAKuUYSwB7=gHmwyJfn45KAAN33gg8zFTsg-LaQzfX9ccYvb3xw@mail.gmail.com>

On Mon, Aug 29, 2011 at 04:38:03PM -0700, Vaibhav Jain wrote:
> On Mon, Aug 29, 2011 at 3:24 PM, Ramesh.P <rameshpa@gmail.com> wrote:
> 
> > Hi Vaibhav,
> >
> > Try /etc/rsyslog.conf. However you should be using
> > /proc/sys/kernel/printk to really configure printk.
> >
[snip]
> 
> Hi Ramesh,
> 
> As I mentioned /etc/syslog.conf is not there on my system. Could you please
> tell me if the name has changed for the file in 2.6 kernel ? Also, does
> /proc/sys/kernel/printk provides for the same level of control ?

Syslog is a user space program, that collects the kernel messages.
So if you don't have /etc/syslog.conf on your system, it likely just
means that you don't have a standard installation of the syslog program,
which can have different reasons. AFAIK, syslog has been replaced by
rsyslog or syslog-ng on modern desktop linux distros.

BTW, Ramesh told you to try /etc/rsyslog.conf (note the 'r'), not
/etc/syslog.conf.

HTH,
	Jonathan Neusch?fer

  parent reply	other threads:[~2011-08-30 19:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-29 15:46 how to configure printk() in 2.6 kernel Vaibhav Jain
2011-08-29 22:24 ` Ramesh.P
2011-08-29 23:38   ` Vaibhav Jain
2011-08-30  4:18     ` Mulyadi Santosa
2011-08-30 19:25     ` Jonathan Neuschäfer [this message]
2011-08-31 20:07       ` Vaibhav Jain
2011-08-31 20:29         ` Jeff Haran
2011-08-31 21:22           ` Vaibhav Jain
2011-08-31 21:35             ` Mirco Tischler

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=20110830192513.GB1732@debian.debian \
    --to=j.neuschaefer@gmx.net \
    --cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.