View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003286unrealircdpublic2007-04-19 02:502015-05-28 18:41
ReporterstskeepsAssigned Tosyzop  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
PlatformAllOSAllOS VersionAll
Product Version3.3-alpha0 
Summary0003286: More intelligent link handling
DescriptionParent bug for more intelligent link handling bugs
TagsNo tags attached.
3rd party modules

Relationships

parent of 0003050 resolvedsyzop alternative hub flag for autoconnects 
parent of 0003132 resolvedsyzop New class option: Max concurrect connection attemptes 
parent of 0001460 closedsyzop leafs and autoconnect... 
parent of 0002213 closedsyzop Conditional Linking Logic 

Activities

stskeeps

2007-04-27 05:01

reporter   ~0013801

My idea for this:

link-control <pattern name>
{
       <key> <value>;
       <key> <value>;
};

and <pattern name> is handled by a module that translates into the corresponding
conf blocks - deny link {}, etc. Syntactic sugar, and maybe extending crule syntax

one could be

link-control fallover
{
       hub hub1;
       hub next_hub_to_try;
       hub third_hub_to_try;
};

syzop

2015-05-28 18:41

administrator   ~0018373

Since 3.2.8 or 3.2.9 it's no longer a problem if you connect to X servers at the same time, UnrealIRCd will deal with it. Previously this resulted in chaos and de-linking servers, but not anymore.

Therefore this is no longer needed. Just put link to all your hubs with autoconnect and with a low connfreq.

Issue History

Date Modified Username Field Change
2007-04-19 02:50 stskeeps New Issue
2007-04-19 02:50 stskeeps Relationship added parent of 0003050
2007-04-19 02:52 stskeeps Relationship added parent of 0003132
2007-04-19 02:58 stskeeps Status new => acknowledged
2007-04-19 03:22 stskeeps Relationship added parent of 0001460
2007-04-27 04:52 stskeeps Relationship added parent of 0002213
2007-04-27 05:01 stskeeps Note Added: 0013801
2015-05-28 18:41 syzop Note Added: 0018373
2015-05-28 18:41 syzop Status acknowledged => closed
2015-05-28 18:41 syzop Assigned To => syzop
2015-05-28 18:41 syzop Resolution open => no change required