Opened 11 years ago

Closed 11 years ago

Last modified 4 years ago

#1922 closed defect (invalid)

2 instances of syslogd Broadcom BCM947xx/953xx [2.4]

Reported by: Weedy <weedy2887@…> Owned by: florian
Priority: normal Milestone: Barrier Breaker 14.07
Component: base system Version:
Keywords: syslogd 2 two processes Cc:


right after boot

126 root 376 S /sbin/syslogd -C16 -m 0
147 root 416 S syslogd -C16

syslogd has a initscript at S01 while its also started in boot at S10. I just put a comment in front of line 17 in /etc/init.d/boot and now I have one process.

126 root        396 S   /sbin/syslogd -C16 -m 0
152 root        376 S   klogd

this might explain why my logbuffer is cleared randomly (switching between the 2 syslogds buffers maybe?). Of course if there is a reason for 2 instances of syslogd i would like to hear it.

Attachments (0)

Change History (6)

comment:1 Changed 11 years ago by florian

  • Owner changed from developers to florian
  • Status changed from new to assigned

It seems like I have only 1 syslogd instance on kamikaze, are you refering to whiterussian ?

comment:2 Changed 11 years ago by Weedy <weedy2887@…>

nvm, this seems to be a webif2 bug.

comment:3 Changed 11 years ago by florian

  • Resolution set to worksforme
  • Status changed from assigned to closed

comment:4 Changed 11 years ago by lubek <lubek@…>

  • Resolution worksforme deleted
  • Status changed from closed to reopened

florian, he refers to webif2 scripts.
Because openwrt lacked a rich syslogd configuration, the syslogd started from rcS was killed and started with many other options with a configuration in /etc/config/syslog in X-Wrt (it was dragged from the white russian).
Moreover after moving it to S10, it misses everything between rcS and S10.
See: and

I would suggest using a standalone syslogd startup script similar to the one used in X-Wrt (we cannot use it as it is because it uses webif2 functions).
I do not want to modify standard scripts in webif2 postinit in kamikaze when we can use a better solution that could satisfy all requirements.

comment:5 Changed 11 years ago by mbm

  • Resolution set to invalid
  • Status changed from reopened to closed

Closing this ticket (again!) as it does not appear to be an openwrt bug, but rather a xwrt bug.

comment:6 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

as closed .
The resolution will be deleted. Next status will be 'reopened'.

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

Note: See TracTickets for help on using tickets.