adam/znc
1
0 Fork 0
mirror of https://github.com/znc/znc.git synced 2026-10-31 01:32:02 +01:00
Code Issues 362 Packages Projects Releases Wiki Activity

Feature request : Finer connection control #54

New Issue
Closed
opened 2026-10-05 03:56:28 +02:00 by adam · 1 comment
adam commented 2026-10-05 03:56:28 +02:00
Owner
Copy link
Copy source

Case 1 : znc automatically connects to networks with IRCConnectEnabled=true in znc.conf, and IRCConnectEnabled is changed to "true" in several cases.

Even if you set IRCConnectEnabled to false, IRCConnectEnabled could be set to true again in znc.conf for currently connected networks when

  1. you execute /znc saveconfig, shutdown, or restart.

  2. you save settings in webadmin.

  3. znc receives SIGUSR1 signal.

If there was a setting like "AutoConnectOnBoot" which, if set to true, makes znc connect automatically during startup,
users don't have to constantly keep an eye on IRCConnectEnable.

Case 2: znc can disconnect from or connect to networks unexpectedly when you make znc rehash.

If IRCConnectEnabled was false for freenode network in znc.conf and you executed "/znc connect" for freenode network,
when you rehash znc, znc would disconnect you from freenode since IRCConnectEnabled is set to false again by rehash.

If rehashes make znc disconnect or connect, users can be easily led to confusions.

Discussion :
The current design can easily confuse users.
If the role of IRCConnectEnabled was restricted and new settings were made for finer control,
users wouldn't experience inconvenience or confusions.

Case 1 : znc automatically connects to networks with IRCConnectEnabled=true in znc.conf, and IRCConnectEnabled is changed to "true" in several cases. Even if you set IRCConnectEnabled to false, IRCConnectEnabled could be set to true again in znc.conf for currently connected networks when 1) you execute /znc saveconfig, shutdown, or restart. 2) you save settings in webadmin. 3) znc receives SIGUSR1 signal. If there was a setting like "AutoConnectOnBoot" which, if set to true, makes znc connect automatically during startup, users don't have to constantly keep an eye on IRCConnectEnable. Case 2: znc can disconnect from or connect to networks unexpectedly when you make znc rehash. If IRCConnectEnabled was false for freenode network in znc.conf and you executed "/znc connect" for freenode network, when you rehash znc, znc would disconnect you from freenode since IRCConnectEnabled is set to false again by rehash. If rehashes make znc disconnect or connect, users can be easily led to confusions. Discussion : The current design can easily confuse users. If the role of IRCConnectEnabled was restricted and new settings were made for finer control, users wouldn't experience inconvenience or confusions. <!-- github-sync-id:3003578 -->
adam closed this issue 2026-10-05 03:56:28 +02:00
adam commented 2026-10-05 03:56:29 +02:00
Author
Owner
Copy link
Copy source

Just don't rehash. Most stuff is configurable through admin/webadmin. Settings that aren't configurable through them, don't need to be changed often.
And do you really need to repeat again and again that incomplete list of situations when ZNC saves its config?
Anyway, this is duplicate of #110. No need to open hundreds of new tickets about the same issue, crocket.

Just don't rehash. Most stuff is configurable through admin/webadmin. Settings that aren't configurable through them, don't need to be changed often. And do you really need to repeat again and again that incomplete list of situations when ZNC saves its config? Anyway, this is duplicate of #110. No need to open hundreds of new tickets about the same issue, crocket. <!-- github-comment-id:3699054 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/znc#54