Modify

Opened 7 years ago

#8991 new defect

Two instances of klogd and syslogd in kamikaze

Reported by: Christoph.Pospiech@… Owned by: developers
Priority: normal Milestone: Bugs Paradise
Component: base system Version: Kamikaze 8.09
Keywords: Cc:

Description

Hi,

I just found that there are two instances of each, klogd and syslogd on my system, one instance is started in /etc/init.d/boot, the other is spawned by init as instructed by /etc/inittab. Sending all 4 demons a SIGTERM causes only two to be re-spawned by init. The re-spawned syslogd is missing the "-C16" option.

I fixed this on my installation by eliminating the calls of syslogd and klogd from /etc/init.d/boot, adding the -C16 option to /etc/inittab. Then I sent a SIGHUP to init (to cause a reread of /etc/inittab) and sent another SIGTERM to syslogd.

I admit that my solution misses 'config_get log_size "$cfg" log_size'. But perhaps this information should go into /etc/syslog.conf anyway. Then init would start syslogd which reads /etc/syslog.conf.

This has been observed on an early build of kamikaze.
uname -a reports
'Linux OpenWrt 2.6.25.16 #1 Wed Aug 27 19:28:16 CEST 2008 mips unknown'.
I am not sure whether it has been already fixed down-stream. But at least I haven't seen another ticket that fits this error.
I opened this ticket to make sure it will be fixed in future versions.

Christoph Pospiech

Attachments (0)

Change History (0)

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.