23 Jan
2019
23 Jan
'19
3:07 p.m.
Ah, that explains it then.
The idea of whitelist ranges is really neat, but I'd still like a way to
put tags or other descriptors in the wl file so you can easily tell what
you're listening to.
I'll work on some ideas -- either setting up a 3rd optional field for
tags, or maybe scanning for "#" and calling anything after that a comment.
Thanks,
John
----
On 1/22/19 5:35 PM, Graham Norbury wrote:
John,
A while back I added the ability for whitelist ranges. The original
format was "tgid" only but it didn't barf if the tag was there as well.
The new format is "tgid1"<tab>"tgig2". If you specify two
tgids on a
line, it is considered an inclusive range from tgid1 to tgid2.
Strip the spurious tags and your file will work ok.
Graham
On Tue, Jan 22, 2019, 3:33 PM John Ackermann N8UR <jra(a)febo.com
<mailto:jra@febo.com> wrote:
Hi --
After a few months away, I fired up the op25 machine today and updated
to the latest boatbod version. Great improvements, especially the web
interface!
I'm having a minor issue, though. It seems as though my whitelist file
is no longer working. The log shows that it's being read, but doesn't
list the included groups, and I'm hearing lots of traffic from TGs that
aren't on the list. Has anything changed in whitelist handling?
(My wl
file is in two column format: TGID<tab>TAG which worked after patches
that Graham applied last year.)
And, by the way, thanks Graham for fixing the statistics.sh script; I
never quite got around to that after the log file format changed.
Thanks,
John