Michael Tokarev wrote:
> It is not the init script, it is the busybox syslog implementation.
> For simplicity, it is one applet that does both syslog function and
> klogd function, and klogd function is not optional.
Er, are you sure?
I'm definitely not familiar with busybox code, but
* /etc/init.d/busybox-{syslogd,klogd} are separate scripts that run separate processes:
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1475 0.0 0.0 4812 420 ? Ss 09:57 0:00 /sbin/klogd
root 1478 0.0 0.4 13008 8632 ? Ss 09:57 0:00 /sbin/syslogd -C8192
* busybox {syslogd,klogd} --help suggests they're separate applets.
* busybox/sysklogd/Config.src has separate options for syslogd and klogd.
* the description for CONFIG_SYSLOGD says
"When used in conjunction with klogd, messages from the Linux
kernel can also be recorded."
which implies it can be used without klogd.
* If I stop klogd, "logger test" still makes "test" appear in logread.
* if I do "make allnoconfig" then in "make menuconfig" I can enable
System Logging Utilities > syslogd without klogd being turned on.
$ ./busybox --help | tail -3
Currently defined functions:
logread, syslogd
$ ./busybox logread | grep user.notice.*test
Sep 29 19:37:11 frey user.notice twb: test
Disclaimer: the source code tests above, I was looking at
1_22_0-191-g26a8b9f because that was what I had in front of me.
The runtime bits I checked on a jessie/sid install.
Attachment:
signature.asc
Description: Digital signature