View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002919 | unreal | ircd | public | 2006-05-20 19:45 | 2016-11-10 09:53 |
| Reporter | syzop | Assigned To | syzop | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | no change required | ||
| Platform | ANY | OS | ANY | OS Version | ANY |
| Product Version | 3.2.5 | ||||
| Summary | 0002919: Extend time synchronization: daily synch | ||||
| Description | Now we have time synchronization support in CVS/willbe-3.2.5, extend it more: - Possibly allow DNS names - Make it auto-synch every 24 hours or so (on/off by default? don't know..) - Maybe more, but.. have no idea :P This would be for 3.2.6, since for 3.2.5 we are done with this stuff for now ;) | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
- Definately allow DNS names. Round robins anyone? (Beats pulling out host/nslookup and copying each and every IP manually, plus you don't have to deal with the random case where a server's IP changes for some reason) ;) - Off by default is probably best. People with drifting clocks can turn it on themselves. - Command to manually synch while the ircd is running? (I'm thinking either /tsctl synch or /rehash) <potentially-stupid-idea> Maybe go as far as have unreal reject links if they are way too far ahead/behind on the clock (ie right now it gives a big warning for splits of ~ 10s or more, but maybe when differences are ~ 30s or 60s or more, just refuse the link to avoid major issues). Of course, this has nothing to do with the built-in clock synching, but could further encourage its use ;) (when you already get a spamload of snotices, it can be easy to miss the "Possible negative TS split blablabla [PLEASE SYNC YOUR CLOCKS!]" spew, but "Error from other.server: Closing Link: you.blah[1.2.3.4] (Excessive TS Split - PLEASE SYNC YOUR CLOCKS)" is a lot more likely to catch someone's attention ;) ). Only problem is that any TS problems from, eg, SJOIN/NICK will have already done their damage by the time the NETINFO is received, but it would certainly avoid any later issues. And in case you ask, I do believe, in fact, some other ircds already drop links that introduce sufficiently large TS splits. </potentially-stupid-idea> |
|
|
Many don't allow a 5 second skew... And to be honest, I think that's probably a good thing. |
|
|
i think if unreal is to reject links that have high differences, it should be configurable (the max skew that is) via the config file ( set::timesynch:maxskew maybe ?), and if not specified, be something like 5 seconds by default |
|
|
Not so sure. Especially given how much it FUCKS with channels when there are desynchs in the time. 10 seconds desynch -> hell with chmode +f. alternately, consider the case where they can choose to not run the NTP/timesynch code, and thus allow desynchs, OR do the timesynch _and_ require the clocks be synched. but even so, I don't think that laziness among irc-admins or shell-admins should be so blithely accepted. I have in the past had to chew out various shell-admins for this problem. |
|
|
If people are going to be lame and let everything desync on purpose, then theres no point in trying to stop them; they will just whine about it; besides, having this configurable _could_ be useful for testing certain things. |
|
|
A long time ago I was the techadmin on an ircnet that had linked with another network, and the admins there had configured everything default and had very little clue of how to fix anything... and I got a lot of shit for stuff breaking, yet I wasn't given access to fix it. Yes, I got out of that arrangement, eventually. But it has made me want to make defaults SANE, not that I mind fixing shit. I kinda like it, but having to deal with people who don't, can't, and don't want to learn... makes life very frustating. we might as well make for a SANE default, even if it IS able to be turned off. Yes, there is also the whole issue of dictating policy in code, and how that is a bad thing... but sometimes I would just want to tell those ppl to bite me. |
|
|
Indeed, i agree with you, there are a lot of n00bs out there who don't have a clue about running an ircd; which is exactly the reason why i suggested that it be defaulted to 5, even if not specified in the config. That should make everyone happy; people would don't know better will get a good default of 5 second max skew on linking, and those who feel they _need_ to change the max skew for whatever reason, can do so. |
|
|
I agree as long as we don't end up with bright-bois telling other ppl to "just turn that code off" as if it were accepted practice. |
|
|
Not considering this anymore. Also max time skew check on link has been implemented in 4.0.0. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2006-05-20 19:45 | syzop | New Issue | |
| 2006-05-20 19:45 | syzop | Relationship added | related to 0002863 |
| 2006-05-20 22:33 | aquanight | Note Added: 0011744 | |
| 2006-05-25 23:33 | tabrisnet | Note Added: 0011779 | |
| 2006-05-31 07:24 | syzop | Relationship added | child of 0002936 |
| 2006-08-22 17:51 | djGrrr | Note Added: 0012212 | |
| 2006-08-22 18:04 | tabrisnet | Note Added: 0012213 | |
| 2006-08-22 18:13 | djGrrr | Note Added: 0012214 | |
| 2006-08-22 18:20 | tabrisnet | Note Added: 0012215 | |
| 2006-08-22 18:27 | djGrrr | Note Added: 0012216 | |
| 2006-11-03 17:40 | syzop | Relationship deleted | child of 0002936 |
| 2007-04-15 17:37 | tabrisnet | Note Added: 0013416 | |
| 2007-04-18 05:29 |
|
Status | new => acknowledged |
| 2016-11-10 09:53 | syzop | Assigned To | => syzop |
| 2016-11-10 09:53 | syzop | Status | acknowledged => closed |
| 2016-11-10 09:53 | syzop | Resolution | open => no change required |
| 2016-11-10 09:53 | syzop | Note Added: 0019507 |
