From: Gary Thomas <gary@mlbassoc.com>
To: Poky <poky@lists.pokylinux.org>
Subject: Useless syslogd
Date: Fri, 11 Feb 2011 13:47:29 -0700 [thread overview]
Message-ID: <4D55A061.8040901@mlbassoc.com> (raw)
... at least out of the box.
It seems that syslog is configured to store its messages in
a buffer (memory only?) by default:
$ cat meta/recipes-core/busybox/files/syslog.conf
DESTINATION="buffer" # log destinations (buffer file remote)
...
This doesn't seem very useful to me. I know I can override this
in my platform recipes, but I was just wondering what's the
rationale? Would it not make more sense to chose DESTINATION="file"?
Otherwise, where do the messages go? How can I see them?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2011-02-11 20:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 20:47 Gary Thomas [this message]
2011-02-11 21:50 ` Useless syslogd Tom Zanussi
2011-02-11 22:26 ` Gary Thomas
2011-02-11 22:27 ` Chris Larson
2011-02-11 22:33 ` Gary Thomas
2011-02-14 17:04 ` Darren Hart
2011-02-14 17:19 ` Gary Thomas
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=4D55A061.8040901@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=poky@lists.pokylinux.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