From: Andrew Lunn <andrew@lunn.ch>
To: Jon Ringle <JRingle@vertical.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] remote syslog support in Redboot?
Date: Thu, 10 May 2007 14:13:00 -0000 [thread overview]
Message-ID: <20070510115617.GA13088@lunn.ch> (raw)
In-Reply-To: <4DD3AF7ECBBC43409BA36508938D0185123B73@CVAEX1.VERTICAL.COM>
On Wed, May 09, 2007 at 03:12:29PM -0400, Jon Ringle wrote:
> Has anyone implemented the ability to have diag_printf() messages be
> sent to a remote syslog server in Redboot/ecos?
You will have to be careful when doing this. diag_printf() uses a very
simple polled IO, blocking serial device driver. The idea is that it
should always work, in any context. So you can do a diag_printf() in
an ISR or a DSR, not just a thread. It is also guaranteed the output
will be out the serial port before diag_printf() returns.
If you somehow modify diag_printf to send over a network stack it is
unlikely you can keep these properties. I would suggest you look at
adding a standard syslog interface, eg:
#include <syslog.h>
void openlog(const char *ident, int option, int facility);
void syslog(int priority, const char *format, ...);
void closelog(void);
#define _BSD_SOURCE
#include <stdarg.h>
void vsyslog(int priority, const char *format, va_list ap);
and don't modify diag_printf().
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2007-05-10 11:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 22:50 Jon Ringle
2007-05-10 14:13 ` Andrew Lunn [this message]
2007-05-10 14:53 ` Jon Ringle
2007-05-10 16:02 ` Gary Thomas
2007-05-10 21:40 ` [ECOS] " Grant Edwards
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=20070510115617.GA13088@lunn.ch \
--to=andrew@lunn.ch \
--cc=JRingle@vertical.com \
--cc=ecos-discuss@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).