[#6417] Busybox syslogd ignores configuration setting for USER_BUSYBOX_FEATURE_IPC_SYSLOG_BUFFER_SIZE(2010)

[#6417] Busybox syslogd ignores configuration setting for USER_BUSYBOX_FEATURE_IPC_SYSLOG_BUFFER_SIZE

Submitted By: Reggy Perrin

Open Date

2010-12-21 14:31:29

Priority:

Medium Assignee:

Nobody

Status:

Open Fixed In Release:

N/A

Found In Release:

2010R1-RC5 Release:

Category:

Kernel Functions Board:

N/A

Processor:

ALL Silicon Revision:

Is this bug repeatable?:

Yes Resolution:

Rejected

Uboot version or rev.:

Toolchain version or rev.:

bfin-uclinux-gcc (ADI/svn-4960

App binary format:

N/A

Summary: Busybox syslogd ignores configuration setting for USER_BUSYBOX_FEATURE_IPC_SYSLOG_BUFFER_SIZE

Details:

If you configure the busybox syslogd to rotate the syslog:

BusyBox --->

System Logging Utilities --->

[*] syslogd

[*] Rotate message files

[ ] Remote Log support

[ ] Support -D (drop dups) option

[*] Circular Buffer support

(2048) Circular buffer size in Kbytes (minimum 4KB)

the Circular buffer size is ignored. To correct, change:

user/busybox/busybox-1.16.2/sysklogd/syslogd.c, lines 126-129

from:

#if ENABLE_FEATURE_ROTATE_LOGFILE

.logFileSize = 200 * 1024,

.logFileRotate = 1,

#endif

to:

#if ENABLE_FEATURE_ROTATE_LOGFILE

.logFileSize = CONFIG_FEATURE_IPC_SYSLOG_BUFFER_SIZE * 1024,

.logFileRotate = 1,

#endif

Follow-ups

--- Mike Frysinger 2010-12-21 14:37:27

this has already been fixed in a newer busybox version such as the one already

in trunk (1.17.x)

--- Mike Frysinger 2010-12-21 19:14:23

hmm, nm, i confused myself with diff aspects of the source. the code you see is

correct. the option is for controlling the circular buffer size in memory. it

has no bearing on the disk size.

if you look a few lines down, you'll see it being used correctly:

.shm_size = ((CONFIG_FEATURE_IPC_SYSLOG_BUFFER_SIZE)*1024), // default shm

size

--- Reggy Perrin 2010-12-22 10:40:16

Mike,

So the disk size is hard-coded? For diagnostics, we are using syslog, and have

a large flash that can hold events. Based on your comments, I think we want:

.shm_size = 16K (or whatever the default is)

.logFileSize = 2M (to record a fairly long events

Any issues with this? Concerns?

--- Reggy Perrin 2010-12-22 10:40:17

Mike,

So the disk size is hard-coded? For diagnostics, we are using syslog, and have

a large flash that can hold events. Based on your comments, I think we want:

.shm_size = 16K (or whatever the default is)

.logFileSize = 2M (to record a fairly long events

Any issues with this? Concerns?

--- Mike Frysinger 2010-12-22 10:52:50

if you dont rotate, then syslog will just keep writing forever. if you rotate,

then the hardcoded limit you see is when the logs will be rotated.

Files

Changes

Commits

Dependencies

Duplicates

Associations