From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] syslog output to serial console
Date: Wed, 21 Aug 2013 23:09:08 +0200 [thread overview]
Message-ID: <52152C74.4080904@mind.be> (raw)
In-Reply-To: <CAJpxd044gjJfXpwbMfC_3VAUU26-DgD+Sex4fACjWGszR2MjPg@mail.gmail.com>
On 21/08/13 22:22, Bryce Schober wrote:
> I realize that this is a bit off-topic...
>
> I've configured my target for boot-loader & linux boot serial console
> output, but now I'd really like to redirect the rest of what gets into
> syslog to the serial console as well. Is there a way to do that with
> busybox syslog?
>
> The primary use-case here is for seeing the output results / errors from
> my set of /etc/init.d scripts, so if it's not feasible to get this
> re-direction up and running early in the boot process, it wouldn't be
> worth it.
Actually, the output of init scripts should already go to the console.
When the kernel mounts the rootfs and calls init, it sends its stdout and
stderr to /dev/console. If your rootfs is an initramfs, however, the
kernel doesn't automount the devtmpfs so /dev/console doesn't exist when
/init is executed. We solve this with the script in fs/cpio/init. If this
is the problem, you'll see that the kernel reports something like "Unable
to find initial console".
The only thing captured by syslog are the messages going to /dev/log,
which are sent out by some daemons. If you want this output to go to
/dev/console as well, you can add something like
::respawn:/usr/bin/tail -50 -F /var/log/messages
to /etc/inittab.
Regards,
Arnout
>
> Thanks for any advice or pointers you can offer...
> <>< <>< <><
> Bryce Schober
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-08-21 21:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 20:22 [Buildroot] syslog output to serial console Bryce Schober
2013-08-21 21:09 ` Arnout Vandecappelle [this message]
2013-08-21 22:52 ` Danomi Manchego
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=52152C74.4080904@mind.be \
--to=arnout@mind.be \
--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.