All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco Montorsi <francesco.montorsi@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] syslog messages during boot not recorded?
Date: Mon, 8 Apr 2013 16:30:28 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130408T181747-784@post.gmane.org> (raw)

Hi all,
I'm using buildroot v10.11 on an embedded system running Linux kernel 
2.6.32.2.

I installed some daemons wrote by me which are started at boot time by some 
/etc/init.d scripts of mine. These daemons use many syslog() to provide 
verbose debugging messages... however, for some reason, when I boot the 
system and cat /var/log/messages, I do not see any message.
If I start manually the daemons, the messages are correctly logged to 
/var/log/messages... 

I think that this problem maybe because syslogd is startd AFTER all 
/etc/init.d scripts have been processed.. is that right?


I tried to comment the lines:

null::respawn:/sbin/syslogd -n -m 0
null::respawn:/sbin/klogd -n

contained in /etc/inittab and then to add the S01logging script found in 
this patch:
http://lists.busybox.net/pipermail/buildroot/2011-July/043828.html

but I obtained the same results... (of course my etc scripts start with S90, 
S91, etc, so they should run AFTER S01logging...)

Thanks for any hint!
Francesco

             reply	other threads:[~2013-04-08 16:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 16:30 Francesco Montorsi [this message]
2013-04-08 16:38 ` [Buildroot] syslog messages during boot not recorded? Gustavo Zacarias
2013-04-08 16:51   ` Francesco
2013-04-08 16:54     ` Gustavo Zacarias
2013-04-09  8:01       ` Francesco
2013-04-09  8:21         ` Francesco
2013-04-11 10:06           ` Francesco Montorsi

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=loom.20130408T181747-784@post.gmane.org \
    --to=francesco.montorsi@gmail.com \
    --cc=buildroot@busybox.net \
    /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.