From: Ni Qingliang <niqingliang@insigma.com.cn>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: does busybox 1.19 still support the arg `-m'?
Date: Wed, 11 Jan 2012 16:16:22 +0800 [thread overview]
Message-ID: <1326269782.12463.4.camel@localhost.localdomain> (raw)
In-Reply-To: <1326269523.12463.3.camel@localhost.localdomain>
and in syslog-startup.conf, the comments `incompatible with busybox'
should be deleted.
#ROTATESIZE=0 # rotate log if grown beyond X [kByte] (incompatible
with busybox)
#ROTATEGENS=3 # keep X generations of rotated logs (incompatible with
busybox)
On Wed, 2012-01-11 at 16:12 +0800, 倪庆亮 wrote:
> in file meta/recipes-core/busybox/files/syslog
> I found code section:
> if [ -n "$MARKINT" ]; then
> SYSLOG_ARGS="$SYSLOG_ARGS -m $MARKINT"
> fi
> but I can't find `-m' in the help of syslogd.
>
>
> syslogd --help
> BusyBox v1.19.3 (2012-01-11 12:34:06 CST) multi-call binary.
>
> Usage: syslogd [OPTIONS]
>
> System logging utility
>
> -n Run in foreground
> -O FILE Log to FILE (default:/var/log/messages)
> -l N Log only messages more urgent than prio N (1-8)
> -S Smaller output
> -s SIZE Max size (KB) before rotation (default:200KB,
> 0=off)
> -b N N rotated logs to keep (default:1, max=99,
> 0=purge)
> -R HOST[:PORT] Log to IP or hostname on PORT (default
> PORT=514/UDP)
> -L Log locally and via network (default is network
> only if)
> -C[size_kb] Log to shared mem buffer (use logread to read
> it)
> -f FILE Use FILE as config (default:/etc/syslog.conf)
>
> --
> Yi Qingliang
> niqingliang@insigma.com.cn
> https://niqingliang2003.wordpress.com
>
--
Yi Qingliang
niqingliang@insigma.com.cn
https://niqingliang2003.wordpress.com
next prev parent reply other threads:[~2012-01-11 8:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 8:12 does busybox 1.19 still support the arg `-m'? Ni Qingliang
2012-01-11 8:16 ` Ni Qingliang [this message]
2012-01-11 19:15 ` Joshua Lock
2012-01-11 19:14 ` Joshua Lock
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=1326269782.12463.4.camel@localhost.localdomain \
--to=niqingliang@insigma.com.cn \
--cc=openembedded-core@lists.openembedded.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