{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":227136655,"defaultBranch":"master","name":"systemd","ownerLogin":"aj-bagwell","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2019-12-10T14:09:36.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/981578?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1610038061.0","currentOid":""},"activityList":{"items":[{"before":"9e006192d5fb927c83a6226bef464d572dd49255","after":"ae5ddc21c3b6f0dc0c03f39ddd0934d544942db8","ref":"refs/heads/ntp","pushedAt":"2023-07-05T12:55:58.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"aj-bagwell","name":"AJ Bagwell","path":"/aj-bagwell","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/981578?s=80&v=4"},"commit":{"message":"timesyncd: Handle low precision NTP servers better\n\nIf the NTP server we are getting time from has a does not conform to\nthe RFC and rounds down  time to a brokenly low precision (e.g. 1\nsecond) then we should not try to sync the local time to the rounded\ntime we get from the server other wise the clock will just keep jumping\naround.\n\nntpdc resolves this by using the precision reported by the server when\ncalculating the offset, so if the server is only report time to one\nsecond it will always jump by a multiple of a second. This does reduce\nthe ammount of jumps but does mean we would never slew as a second is\nbigger than NTP_MAX_ADJUST of 0.4.\n\nInstead I opted to ignore any offest less than the precision of the\nserver and subract the precision from the offset. This will cause the\nclient to slew nicely to one end of the window given by the precision\ndepending on if it is slightly fast or slightly slow.\n\nFixes systemd#14404.","shortMessageHtmlLink":"timesyncd: Handle low precision NTP servers better"}},{"before":"e79713c482cc22b9507e7b4ef13f89af2ca0da41","after":"9e006192d5fb927c83a6226bef464d572dd49255","ref":"refs/heads/ntp","pushedAt":"2023-07-05T11:30:42.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"aj-bagwell","name":"AJ Bagwell","path":"/aj-bagwell","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/981578?s=80&v=4"},"commit":{"message":"timesyncd: Handle low precision NTP servers better\n\nIf the NTP server we are getting time from has a does not conform to\nthe RFC and rounds down  time to a brokenly low precision (e.g. 1\nsecond) then we should not try to sync the local time to the rounded\ntime we get from the server other wise the clock will just keep jumping\naround.\n\nntpdc resolves this by using the precision reported by the server when\ncalculating the offset, so if the server is only report time to one\nsecond it will always jump by a multiple of a second. This does reduce\nthe ammount of jumps but does mean we would never slew as a second is\nbigger than NTP_MAX_ADJUST of 0.4.\n\nInstead I opted to ignore any offest less than the precision of the\nserver and subract the precision from the offset. This will cause the\nclient to slew nicely to one end of the window given by the precision\ndepending on if it is slightly fast or slightly slow.\n\nFixes systemd#14404.","shortMessageHtmlLink":"timesyncd: Handle low precision NTP servers better"}},{"before":"b00ae43e8f896345ea0ed6634b54e0f9efa9c65f","after":"e79713c482cc22b9507e7b4ef13f89af2ca0da41","ref":"refs/heads/ntp","pushedAt":"2023-07-05T11:24:54.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"aj-bagwell","name":"AJ Bagwell","path":"/aj-bagwell","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/981578?s=80&v=4"},"commit":{"message":"timesyncd: Handle low precision NTP servers better\n\nIf the NTP server we are getting time from has a does not conform to\nthe RFC and rounds down  time to a brokenly low precision (e.g. 1\nsecond) then we should not try to sync the local time to the rounded\ntime we get from the server other wise the clock will just keep jumping\naround.\n\nntpdc resolves this by using the precision reported by the server when\ncalculating the offset, so if the server is only report time to one\nsecond it will always jump by a multiple of a second. This does reduce\nthe ammount of jumps but does mean we would never slew as a second is\nbigger than NTP_MAX_ADJUST of 0.4.\n\nInstead I opted to ignore any offest less than the precision of the\nserver and subract the precision from the offset. This will cause the\nclient to slew nicely to one end of the window given by the precision\ndepending on if it is slightly fast or slightly slow.\n\nFixes systemd#14404.","shortMessageHtmlLink":"timesyncd: Handle low precision NTP servers better"}},{"before":"03c1b46f2538b7dc78e08c33f4036ddeec57e83b","after":"b00ae43e8f896345ea0ed6634b54e0f9efa9c65f","ref":"refs/heads/ntp","pushedAt":"2023-06-14T09:53:57.854Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"aj-bagwell","name":"AJ Bagwell","path":"/aj-bagwell","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/981578?s=80&v=4"},"commit":{"message":"timesyncd: Handle low precision NTP servers better\n\nIf the NTP server we are getting time from has a low precision (e.g. 1\nsecond) then we should not try to sync the local time to the rounded\ndown time we get from the server other wise the clock will just keep\njumping around.\n\nntpdc resolves this by using the precision reported by the server when\ncalculating the offset, so if the server is only report time to one\nsecond it will always jump by a multiple of a second. This does reduce\nthe ammount of jumps but does mean we would never slew as a second is\nbigger than NTP_MAX_ADJUST of 0.4.\n\nInstead I opted to ignore any offest less than the precision of the\nserver and subract the precision from the offset. This will cause the\nclient to slew nicely to one end of the window given by the precision\ndepending on if it is slightly fast or slightly slow.\n\nFixes systemd#14404.","shortMessageHtmlLink":"timesyncd: Handle low precision NTP servers better"}},{"before":"90a63642839a240eb4e9d3760ed4242c2f118449","after":"03c1b46f2538b7dc78e08c33f4036ddeec57e83b","ref":"refs/heads/ntp","pushedAt":"2023-04-03T08:48:58.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"aj-bagwell","name":"AJ Bagwell","path":"/aj-bagwell","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/981578?s=80&v=4"},"commit":{"message":"timesyncd: Handle low precision NTP servers better\n\nIf the NTP server we are getting time from has a low precision (e.g. 1\nsecond) then we should not try to sync the local time to the rounded\ndown time we get from the server other wise the clock will just keep\njumping around.\n\nntpdc resolves this by using the precision reported by the server when\ncalculating the offset, so if the server is only report time to one\nsecond it will always jump by a multiple of a second. This does reduce\nthe ammount of jumps but does mean we would never slew as a second is\nbigger than NTP_MAX_ADJUST of 0.4.\n\nInstead I opted to ignore any offest less than the precision of the\nserver and subract the precision from the offset. This will cause the\nclient to slew nicely to one end of the window given by the precision\ndepending on if it is slightly fast or slightly slow.\n\nFixes systemd#14404.","shortMessageHtmlLink":"timesyncd: Handle low precision NTP servers better"}},{"before":"4c137ad21703da48c7934f95cad25ec303550c56","after":"90a63642839a240eb4e9d3760ed4242c2f118449","ref":"refs/heads/ntp","pushedAt":"2023-04-03T08:41:04.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"aj-bagwell","name":"AJ Bagwell","path":"/aj-bagwell","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/981578?s=80&v=4"},"commit":{"message":"timesyncd: Handle low precision NTP servers better\n\nIf the NTP server we are getting time from has a low precision (e.g. 1\nsecond) then we should not try to sync the local time to the rounded\ndown time we get from the server other wise the clock will just keep\njumping around.\n\nntpdc resolves this by using the precision reported by the server when\ncalculating the offset, so if the server is only report time to one\nsecond it will always jump by a multiple of a second. This does reduce\nthe ammount of jumps but does mean we would never slew as a second is\nbigger than NTP_MAX_ADJUST of 0.4.\n\nInstead I opted to ignore any offest less than the precision of the\nserver and subract the precision from the offset. This will cause the\nclient to slew nicely to one end of the window given by the precision\ndepending on if it is slightly fast or slightly slow.\n\nFixes systemd#14404.","shortMessageHtmlLink":"timesyncd: Handle low precision NTP servers better"}},{"before":"a3066326efd33b0bee90e71b5f0ca603565716dd","after":"4c137ad21703da48c7934f95cad25ec303550c56","ref":"refs/heads/ntp","pushedAt":"2023-04-03T08:35:44.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"aj-bagwell","name":"AJ Bagwell","path":"/aj-bagwell","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/981578?s=80&v=4"},"commit":{"message":"timesyncd: Handle low precision NTP servers better\n\nIf the NTP server we are getting time from has a low precision (e.g. 1\nsecond) then we should not try to sync the local time to the rounded\ndown time we get from the server other wise the clock will just keep\njumping around.\n\nntpdc resolves this by using the precision reported by the server when\ncalculating the offset, so if the server is only report time to one\nsecond it will always jump by a multiple of a second. This does reduce\nthe ammount of jumps but does mean we would never slew as a second is\nbigger than NTP_MAX_ADJUST of 0.4.\n\nInstead I opted to ignore any offest less than the precision of the\nserver and subract the precision from the offset. This will cause the\nclient to slew nicely to one end of the window given by the precision\ndepending on if it is slightly fast or slightly slow.\n\nFixes systemd#14404.","shortMessageHtmlLink":"timesyncd: Handle low precision NTP servers better"}},{"before":"8fd15cead1fe866737d6b1783f79250193e305d0","after":"a3066326efd33b0bee90e71b5f0ca603565716dd","ref":"refs/heads/ntp","pushedAt":"2023-04-03T08:31:50.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"aj-bagwell","name":"AJ Bagwell","path":"/aj-bagwell","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/981578?s=80&v=4"},"commit":{"message":"timesyncd: Handle low precision NTP servers better\n\nIf the NTP server we are getting time from has a low precision (e.g. 1\nsecond) then we should not try to sync the local time to the rounded\ndown time we get from the server other wise the clock will just keep\njumping around.\n\nntpdc resolves this by using the precision reported by the server when\ncalculating the offset, so if the server is only report time to one\nsecond it will always jump by a multiple of a second. This does reduce\nthe ammount of jumps but does mean we would never slew as a second is\nbigger than NTP_MAX_ADJUST of 0.4.\n\nInstead I opted to ignore any offest less than the precision of the\nserver and subract the precision from the offset. This will cause the\nclient to slew nicely to one end of the window given by the precision\ndepending on if it is slightly fast or slightly slow.\n\nFixes systemd#14404.","shortMessageHtmlLink":"timesyncd: Handle low precision NTP servers better"}},{"before":"5c9ba45123673c98b4cb6b59d34c848e05f1ed31","after":"8fd15cead1fe866737d6b1783f79250193e305d0","ref":"refs/heads/ntp","pushedAt":"2023-04-03T08:27:01.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"aj-bagwell","name":"AJ Bagwell","path":"/aj-bagwell","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/981578?s=80&v=4"},"commit":{"message":"timesyncd: Handle low precision NTP servers better\n\nIf the NTP server we are getting time from has a low precision (e.g. 1\nsecond) then we should not try to sync the local time to the rounded\ndown time we get from the server other wise the clock will just keep\njumping around.\n\nntpdc resolves this by using the precision reported by the server when\ncalculating the offset, so if the server is only report time to one\nsecond it will always jump by a multiple of a second. This does reduce\nthe ammount of jumps but does mean we would never slew as a second is\nbigger than NTP_MAX_ADJUST of 0.4.\n\nInstead I opted to ignore any offest less than the precision of the\nserver and subract the precision from the offset. This will cause the\nclient to slew nicely to one end of the window given by the precision\ndepending on if it is slightly fast or slightly slow.\n\nFixes systemd#14404.","shortMessageHtmlLink":"timesyncd: Handle low precision NTP servers better"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAADTzbJUQA","startCursor":null,"endCursor":null}},"title":"Activity · aj-bagwell/systemd"}