Azure Jane Lunatic (Azz) 🌺 (![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
azurelunatic) wrote2015-05-01 01:44 am
azurelunatic) wrote2015-05-01 01:44 am
Entry tags:
The LAGCHK, the *watch module, and me
So ryan has ZNC set up on his server and I've got an account there. He upgraded this week, and suddenly I was getting flooded with LAGCHK messages every few minutes. It added up.
Now, there is a module that is supposed to fix getting spammed with LAGCHK messages, and he found the new one, compiled it, installed it, and restarted everything. But I was still getting it.
Eventually I realized that all of this was happening in my *highlight window, which meant that something in my *watch rules was causing it.
That caused a little tiny bell to go ding ding ding somewhere in the back of my head. This had happened before, and I'd had to set up some filtering so it wouldn't do the thing. But why was it doing the thing again now? Surely my settings were still where they were supposed to be...
Turns out my settings on the *one* server were intact, but my settings on the *other* server were not so much.
By that time I'd remembered what I'd done: I'd manually specified that the highlight should only work in specific channels I was in. I decided that I would set it up by manually listing the channels straight off, and try doing wildcards later.
So the short version of the conversation wound up being like:
Azz: /msg *watch list
*watch: 1 *!*@* *highlight *%nick%*
Azz: /msg *watch SETSOURCES 1 #adventuresofstnono #otherrandomchannel
1 here is the ID number of that line, and the line with *%nick%* in it was the one that was setting it off. I'm not actually in multiple channels besides #adventuresofstnono over there, but the second one's there for the sake of syntax example.
ryan has ZNC set up on his server and I've got an account there. He upgraded this week, and suddenly I was getting flooded with LAGCHK messages every few minutes. It added up. Now, there is a module that is supposed to fix getting spammed with LAGCHK messages, and he found the new one, compiled it, installed it, and restarted everything. But I was still getting it.
Eventually I realized that all of this was happening in my *highlight window, which meant that something in my *watch rules was causing it.
That caused a little tiny bell to go ding ding ding somewhere in the back of my head. This had happened before, and I'd had to set up some filtering so it wouldn't do the thing. But why was it doing the thing again now? Surely my settings were still where they were supposed to be...
Turns out my settings on the *one* server were intact, but my settings on the *other* server were not so much.
By that time I'd remembered what I'd done: I'd manually specified that the highlight should only work in specific channels I was in. I decided that I would set it up by manually listing the channels straight off, and try doing wildcards later.
So the short version of the conversation wound up being like:
Azz: /msg *watch list
*watch: 1 *!*@* *highlight *%nick%*
Azz: /msg *watch SETSOURCES 1 #adventuresofstnono #otherrandomchannel
1 here is the ID number of that line, and the line with *%nick%* in it was the one that was setting it off. I'm not actually in multiple channels besides #adventuresofstnono over there, but the second one's there for the sake of syntax example.