How do I flush (clear) the send queue so I don't have to wait 10 minutes for all the messages I flooded it with to go thru? (it's the 3rd time I do this, restarting every time is not an option)
How do I flush (clear) the send queue so I don't have to wait 10 minutes for all the messages I flooded it with to go thru? (it's the 3rd time I do this, restarting every time is not an option)
## <bountysource-plugin>
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/6623231-flush-send-queue?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).
</bountysource-plugin>
<!-- github-sync-id:50442715 -->
I think the question is not switching network, but clearning send queue of ZNC. With WeeChat this is done with /server deloutq which has help text deloutq: delete messages out queue for all servers (all messages WeeChat is currently sending).
I think the question is not switching network, but clearning send queue of ZNC. With WeeChat this is done with `/server deloutq` which has help text `deloutq: delete messages out queue for all servers (all messages WeeChat is currently sending)`.
<!-- github-comment-id:64978833 -->
If to clear the queue, will it make any inconsistent state?
Probably only some messages can be removed from it, while leaving e.g. PONG in place.
If to clear the queue, will it make any inconsistent state?
Probably only some messages can be removed from it, while leaving e.g. PONG in place.
<!-- github-comment-id:65006991 -->
I think that PRIVMSGs are what are being aimed. If you /exec -o something floody from your client, you can abort it using commands like /sever deloutq.
I am not sure would ZNC-level command help unless client flood control or whatever send-delay it is was disabled.
I think that PRIVMSGs are what are being aimed. If you `/exec -o` something floody from your client, you can abort it using commands like `/sever deloutq`.
I am not sure would ZNC-level command help unless client flood control or whatever send-delay it is was disabled.
<!-- github-comment-id:65019141 -->
If you have a bot that doesn't have a send queue (yep, ppl do that, even if you bug them for a week nonstop) you're pretty much fucked and ZNC does the delaying for you
If you have a bot that doesn't have a send queue (yep, ppl do that, even if you bug them for a week nonstop) you're pretty much fucked and ZNC does the delaying for you
<!-- github-comment-id:65019422 -->
ZNC has flood protection and because of that I have disabled send queue in WeeChat so it floods ZNC with everything and accidents such as described before can happen.
ZNC has flood protection and because of that I have disabled send queue in WeeChat so it floods ZNC with everything and accidents such as described before can happen.
<!-- github-comment-id:138898738 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
How do I flush (clear) the send queue so I don't have to wait 10 minutes for all the messages I flooded it with to go thru? (it's the 3rd time I do this, restarting every time is not an option)
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
/msg *status jump?@KindOne- doesn't work
Tested myself, can confirm it doesn't work. It jumps after the... spam has ended.
I think the question is not switching network, but clearning send queue of ZNC. With WeeChat this is done with
/server deloutqwhich has help textdeloutq: delete messages out queue for all servers (all messages WeeChat is currently sending).If to clear the queue, will it make any inconsistent state?
Probably only some messages can be removed from it, while leaving e.g. PONG in place.
I think that PRIVMSGs are what are being aimed. If you
/exec -osomething floody from your client, you can abort it using commands like/sever deloutq.I am not sure would ZNC-level command help unless client flood control or whatever send-delay it is was disabled.
If you have a bot that doesn't have a send queue (yep, ppl do that, even if you bug them for a week nonstop) you're pretty much fucked and ZNC does the delaying for you
ZNC has flood protection and because of that I have disabled send queue in WeeChat so it floods ZNC with everything and accidents such as described before can happen.