View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005292 | unreal | ircd | public | 2019-05-19 16:37 | 2024-09-23 12:40 |
| Reporter | syzop | Assigned To | syzop | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | resolved | Resolution | fixed | ||
| Fixed in Version | 6.1.1 | ||||
| Summary | 0005292: U5: Delay connecting users on server boot | ||||
| Description | It would be nice if we could delay users (eg: temporary handshake delay) if the server just booted up. This gives the server a chance to link with other servers. That way, services CAN be available right from the start, instead of afterwards, and makes a bit more clean restart experience... or at least theoretically. | ||||
| Additional Information | Note that if you handshake delay all connections, then it would also delay incoming server connections. Similarly, if you don't handshake delay but delay the final register (so after CAP END or after all USER & NICK) then 'sasl' was already announced as not available, so is not perfect either. Also, it assumes services link in back fast enough... | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
Dropped as U5 target. |
|
|
This was done 1,5 years ago: commit 2c73a37ac796752b2859b33292d702ff48a48566 Author: Bram Matthys <[email protected]> Date: Sun May 7 11:21:22 2023 +0200 * New setting set::handshake-boot-delay https://www.unrealircd.org/docs/Set_block#set%3A%3Ahandshake-boot-delay which allows server linking autoconnects to kick in (and incoming servers on serversonly ports), before allowing clients in. This potentially avoids part of the mess when initially linking on-boot. This option is not turned on by default, you have to set it explicitly. * This is not a useful feature on hubs, as they don't have clients. * It can be useful on client servers, if you `autoconnect` to your hub. * If you connect services to a server with clients this can be useful as well, especially in single-server setups. You would have to set a low `retrywait` in your anope conf (or similar services package) of like `5s` instead of the default `60s`. Then after an IRCd restart, your services link in before your clients and your IRC users have SASL available straight from the start. |
|
|
private -> public |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-05-19 16:37 | syzop | New Issue | |
| 2019-05-19 16:37 | syzop | Status | new => acknowledged |
| 2019-05-19 16:37 | syzop | Relationship added | child of 0005279 |
| 2019-11-15 06:57 | syzop | Relationship deleted | child of 0005279 |
| 2019-11-18 14:36 | syzop | Note Added: 0021076 | |
| 2024-09-23 12:39 | syzop | Assigned To | => syzop |
| 2024-09-23 12:39 | syzop | Status | acknowledged => resolved |
| 2024-09-23 12:39 | syzop | Resolution | open => fixed |
| 2024-09-23 12:39 | syzop | Fixed in Version | => 6.1.1 |
| 2024-09-23 12:39 | syzop | Note Added: 0023369 | |
| 2024-09-23 12:40 | syzop | View Status | private => public |
| 2024-09-23 12:40 | syzop | Note Added: 0023370 | |
| 2024-09-23 12:40 | syzop | Note Edited: 0023370 |
