Opened 13 years ago

Closed 12 years ago

#37 closed enhancement (wontfix)

Handle repeating error/warning messages

Reported by: ph3-der-loewe Owned by: ph3-der-loewe
Priority: wishlist Milestone:
Component: libroar and friends Version: current
Keywords: syslog rsyslogd Cc:
Architecture: Compiler:
Difficulty: hard Kernel:
Operating System: Parent Tickets:
Patch attached: no Protocol:
Sound driver: Topic: New feature


Currently error and warning messages are printed every time. If the message is repeating like for example underrun warnings does very often this will print out some MB per min of the same message over and over again.

some syslogs started to remove the 'last message repeated N times' feature.

We also got asked to add some logic to implement this on our own.
Yet no algo to do this has been decided.


Change History (6)

comment:1 Changed 12 years ago by ph3-der-loewe

  • Component changed from roard to libroar and friends
  • Type changed from defect to enhancement

This should be handled in the debug layer in libroar.

comment:2 Changed 12 years ago by ph3-der-loewe

  • Priority changed from major to medium

downgrading to prio normal as nobody seems to care at the moment.

comment:3 Changed 12 years ago by ph3-der-loewe

  • Difficulty set to normal

comment:4 Changed 12 years ago by ph3-der-loewe

Is this bug really relevant to major release 0.4? Should such a big change be delayed to 1.0*?

Also nobody seems to care about this.
What is the status of the syslog daemons?

comment:5 Changed 12 years ago by ph3-der-loewe

  • Difficulty changed from normal to hard
  • Keywords syslog rsyslogd added
  • Milestone RoarAudio major release 0.4 deleted
  • Priority changed from medium to wishlist

This is now about a year old and nobody seems to care. It stops the 0.4* release process so I unassign it from the milestone.

comment:6 Changed 12 years ago by ph3-der-loewe

  • Keywords changed from syslog, rsyslogd to syslog rsyslogd
  • Resolution set to wontfix
  • Status changed from new to closed

I'm closing this now as nobody seems to care. Feel free to reopen this bug if you think it still applies.

Note: See TracTickets for help on using tickets.