linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David McCullough <David_Mccullough@securecomputing.com>
To: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
Cc: zaphod001@gmail.com, linux-embedded@vger.kernel.org
Subject: Re: syslog for embedded
Date: Tue, 14 Jul 2009 20:48:52 +1000	[thread overview]
Message-ID: <20090714104852.GA15488@securecomputing.com> (raw)
In-Reply-To: <e4c675870907140323x7e9846d3hb09a89fda239b984@mail.gmail.com>


Jivin Roberto A. Foglietta lays it down ...
> 2009/7/14 Zaphod <zaphod001@gmail.com>:
> > Hi All,
> >
> > i am trying to find good syslog suitable for embedded.
> > Means,
> > 1. no use of dynamic allocations
> > 2. small footprint
> > 3. redirection to multiple destination (number of IPs, file, console)
> >
> > Thanks everyone for help.
> 
>  AFAIK busbox syslogd miss the 3rd requirement. If any other existing
> syslog still miss at least one of the requirements  then upgrading
> busybox with the network support would be a viable solution.

The version of busybox that is included in the uClinux-dist:

	http://www.uclinux.org/pub/uClinux/dist/

has extensions to do most if not all of 3.  I can't recall how much of
that functionality has made it back upstream.

You can have a peek at a much older version of uCLinux-dist at:

	http://cvs.uclinux.org/cgi-bin/cvsweb.cgi/uClinux-dist/user/busybox/

might save the big download,

Cheers,
Davidm

-- 
David McCullough,  david_mccullough@securecomputing.com,  Ph:+61 734352815
McAfee - SnapGear  http://www.snapgear.com                http://www.uCdot.org

      reply	other threads:[~2009-07-14 10:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14 10:01 syslog for embedded Zaphod
2009-07-14 10:23 ` Roberto A. Foglietta
2009-07-14 10:48   ` David McCullough [this message]

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=20090714104852.GA15488@securecomputing.com \
    --to=david_mccullough@securecomputing.com \
    --cc=linux-embedded@vger.kernel.org \
    --cc=roberto.foglietta@gmail.com \
    --cc=zaphod001@gmail.com \
    /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 NNTP newsgroup(s).