[Dxspider-support] badnode filtering

[Klaus Heintzenberg]

Am Samstag, 14. November 2009 12:53:18 schrieben Sie:
> Mike McCarthy, W1NR wrote:
> > I am trying to stop the flood of garbage originating on DXSummit (OH8X)
> > by setting the node in the badnode database. However, the spots from
> > OH8X-11 and other SSID variants still go through. Is there something
> > wrong with the badnode filtering?
> >
> > Am I correct in assuming the following originates on OH8X, relayed by
> > VE1DXI?
> >
> > <- I VE1DXI PC11^1823.2^W7ASS^12-Nov-2009^0005Z^U ARE SUCH A LOSER
> > !!^LO5ER^OH8X-11^H98^~
>
> Ah, I see the problem... It's not the code in the node that is at fault,
> it is the command set/badnode! This is now fixed in cvs/git. No restart
> required.
>
> You may also find that a 'rej/spot node_default call_dxcc 666 or by_dxcc
> 666' useful. This should remove all spots by countries that it doesn't
> recognise - HOWEVER - this may remove some actual DX (usually of the
> commemorative callsign type).
>
> Dirk
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at dxcluster.org
> http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support


Hi!

Ran into some problem when I tried to update badnode.pl.

did  git pull

remote: Counting objects: 29, done. 
remote: Compressing objects: 100% (17/17), done
remote: Total 17 (delta 14), reused 0 (delta 0)
Unpacking objects; 100% (17/17), done
From git://scm.dxcluster.org/scm/spider
4b2584a..47383be  master    -> origin/master
4b2584a..47383be  spider    -> origin/spider
Updating 4b2584a..47383be
error: Entry 'cmd/set/badnode.pl' not uptodate. Cannot merge

Tried to erase badnode.pl before git pull, however still 'cannot merge'

How can I fix the situation?

73, Klaus (dj6rx)