mythbuntu-bugs team mailing list archive

[Foppe Benedictus <603468@xxxxxxxxxxxxxxxxxx>]

Yes I understand that my problem is a hardware problem, I guess partly
heat, but that is not what I am reporting. My problem here is that the
syslog file becomes not readable because it explodes in size with 130
rows per minute added. I do not know if lirc is putting these messages
in the log file or it is udev or something else, but when stopping lirc
the message overflow stops also.

-- 
Lirc too verbose when crashing
https://bugs.launchpad.net/bugs/603468
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in ubuntu.

Status in “lirc” package in Ubuntu: Incomplete

Bug description:
Binary package hint: lirc

My lirc sort of crashed, I do not know what happened, so need to figure that out before reporting a bug report about that. When searching for the problem I found my syslog file blown up to 1.2 Gb and also messages log file was huge.
I will not post my complete syslog, but I made a one cycle snapshot, that is put into syslog 8 times per minute! I do not think that the information put into the logfile is of any use when it is making it almost impossible to open with the logfilereader. Is there any option in letting Lirc not spitting out this much information?