#16863: udpxy is flooting /tmp/log
------------------------+-------------------------------------
Reporter: anonymous | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Barrier Breaker (trunk)
Component: packages | Version: Trunk
Resolution: | Keywords:
------------------------+-------------------------------------
Comment (by anonymous):
Replying to [comment:5 noltari@…]:
> I checked udpxy code and passing a log file enables all these flooding
logs no matter what verbose setting is or not enabled.
>
> So, in order to fix this and have a log file with reasonable logs, udpxy
would need to be significantly modified.
>
> I commented out most settings in order to use the default values, like
it was before udpxy config was introduced.
>
> Regards,
> Álvaro.
That was what I thought, because you guys changed the init.d script some
weeks ago I think, and before that, it had just one simple start argument
without any options at all, therefor no log, and therefor no one noticed
it writing the ram/log full.
Another thing Ive noticed which is "new", udpxy process is now 3-4
processes (before it was always just one) and in sum it takes way more cpu
than back before (now around 20%, before ~6%). It's also weird because the
amount of processes seem to switch. If it's started: 1, when you open a
stream: 3, when you switch channel: 4, after a random time it's back to 3,
than suddenly 2.
--
Ticket URL: <https://dev.openwrt.org/ticket/16863#comment:6>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
