gargoyle-ispy 2017-February-10 18:45.torrent

[ispyisail]

USE AT YOUR OWN RISK

WARNING: DO NOT PRESERVE SETTINGS

Do not install on 4MB routers

gargoyle-ispy 2017-February-10 18:45.torrent
https://goo.gl/xdX8pV


magnet:?xt=urn:btih:02cdc3bbf46f1c3b908ab5b7bf1de9d79e525d39&dn=gargoyle-ispy%202017-February-10%2018_45.7z&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a80&tr=udp%3a%2f%2fopen.demonii.com%3a1337&tr=udp%3a%2f%2ftracker.coppersurfer.tk%3a6969&tr=udp%3a%2f%2ftracker.leechers-paradise.org%3a6969

Routers
https://goo.gl/7SvtsA

Changes
https://github.com/ericpaulbishop/gargo ... its/master

[rseiler]

Surprise!
viewtopic.php?f=3&t=10814

[Lantis]

This torrent is essentially the equivalent of 1.9.2. I won't mirror this one, wait for the next fix

[rseiler]

I'm using 1.9.2, but regarding the "convert email plugin to use new gui" change in the link above, I think something might have gone wrong in the process. Can you confirm?

"Bandwidth usage" is missing. Normally, it follows ARP. As a result, Display Interval and Number of Rows are unusable.



BTW, is there anything to tweak so that "daemon.err uhttpd[1580]: sh: write error: Broken pipe" lines don't blow out the syslog? Those errors can multiply like crazy sometimes when using the UI. Perhaps something to limit the line to one occurrence?

[Lantis]

Looks like it is missing. Have reported.

The kernel already does rate limiting on error messages as far as I knew.
Broken pipe errors are hard to remove, but are harmless

[rseiler]

Wouldn't this be more a syslog thing than a kernel log thing? I don't know, but there definitely isn't any limiting for whichever this is.

Here's the line in 'ps' that I'm guessing pertains:
/sbin/logd -S 16

And even though that's logd and not syslogd (maybe they're the same?), this may be the usage syntax for it:
https://wiki.openwrt.org/doc/howto/log.essentials

-D (Drop duplicates) would probably mask this problem, which I don't think is going to be resolved anytime soon, since there are old OpenWRT threads about it, and I even found it mentioned in the context of LEDE!

If that's all correct, then I guess the question is where that can be added. Perhaps /etc/init.d/log.

[lceron80]

the usb2/sata is not working in this release, going back to the previous build does... any ideas? wrt1200ac

[Lantis]

the usb2/sata is not working in this release, going back to the previous build does... any ideas? wrt1200ac

I suspect this "fix" has caused you a problem.
You'll need to report it upstream at openwrt
http://git.openwrt.org/?p=15.05/openwrt ... d03ece3373

[rseiler]

If that's all correct, then I guess the question is where that can be added. Perhaps /etc/init.d/log.

So I added it to the two relevant lines in that file, rebooted, and did a ps to ensure that it took. It does show it correctly:
/sbin/logd -D -S 16

Unfortunately, it has no effect. Without being able to find any formal usage for logd specifically to know whether it even supports -D, this may or may not be expected.

[tapper]

the usb2/sata is not working in this release, going back to the previous build does... any ideas? wrt1200ac

Hi mate I have a wrt1900AC v2 I will do a test. Thanks for the bug report!