[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: why does syslogd consult /var/run/loglevel?
From:       "Robert P. J. Day" <rpjday () crashcourse ! ca>
Date:       2008-08-21 8:57:37
Message-ID: alpine.LFD.1.10.0808210457180.9688 () localhost ! localdomain
[Download RAW message or body]

On Thu, 21 Aug 2008, Denys Vlasenko wrote:

> On Wednesday 20 August 2008 23:15, Robert P. J. Day wrote:
> >
> >   a colleague showed me an embedded system he was working on that is
> > based on busybox-1.1.3, and was wondering why he wasn't getting his
> > DEBUG-level messages logged to /var/log/messages.  while i was getting
> > ready to explain stuff like /proc/sys/kernel/printk to him, he got an
> > email from one of his co-workers telling him to:
> >
> >   echo "7" > /var/run/loglevel
> >   killall HUP syslogd
> >
> > or something to that effect.  and it worked.
> >
> >   huh?  where exactly does syslogd consult /var/run/loglevel?
>
> I don't see it anywhere in the source.
>
> >   i
> > downloaded the source and poked around, and i don't see any reference
> > to that file.  am i just being dense?  why did that work?  thanks.
>
> Maybe /var/run/loglevel is a symlink to /proc/sys/kernel/printk
> or some such?

upon further examination, it is a local patch to busybox.

rday
--

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================
_______________________________________________
busybox mailing list
busybox@busybox.net
http://busybox.net/cgi-bin/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]