Feature Req: Slow Shutdown #50

New Issue

2026-10-05T03:56:11+02:00

adam commented

2026-10-05 03:56:11 +02:00

Can it be implemented with a command /msg *status slowshutdown
that instead of quitting from every network at the same time, znc will slowly quit from each network at a random timer between 1-5 seconds perhaps?

Can it be implemented with a command /msg *status slowshutdown that instead of quitting from every network at the same time, znc will slowly quit from each network at a random timer between 1-5 seconds perhaps?

adam closed this issue

2026-10-05 03:56:11 +02:00

adam commented

2026-10-05 03:56:12 +02:00

I'm curious: Why?

I'm curious: Why?

adam commented

2026-10-05 03:56:13 +02:00

more or less a privacy concern. Avoiding being linked to certain nicknames when they all quit at the same exact time constantly. This way you can avoid that to a little greater extent.

more or less a privacy concern. Avoiding being linked to certain nicknames when they all quit at the same exact time constantly. This way you can avoid that to a little greater extent.

adam commented

2026-10-05 03:56:13 +02:00

I like the concept, but its pointless if the server was shutdown or if there would be any networking issues causing all the connections to drop.

I like the concept, but its pointless if the server was shutdown or if there would be any networking issues causing all the connections to drop.

adam commented

2026-10-05 03:56:14 +02:00

i see your point. Perhaps apply this usage to a restart command instead of shutdown. This would increment through each network and send a quit in X seconds. Upon connecting again, do the same thing.

i see your point. Perhaps apply this usage to a restart command instead of shutdown. This would increment through each network and send a quit in X seconds. Upon connecting again, do the same thing.

adam commented

2026-10-05 03:56:15 +02:00

I am going to close this because it is unrealistic, if there are any networking issues or stability issues causing every user to disconnect, it will be impossible to do this.

I am going to close this because it is unrealistic, if there are any networking issues or stability issues causing every user to disconnect, it will be impossible to do this.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/znc#50