Network Services | ntpd: Syncing with a server that has a sufficiently negative time offset causes that server to be rate-limited (#12)

[Kinsey Moore (@opticron)]

Kinsey Moore created an issue: https://gitlab.rtems.org/rtems/pkg/rtems-net-services/-/issues/12

Assignee: Kinsey Moore

## Summary
When syncing with a server whose relative time is in the past by more than a trivial amount (more than a minute or two) and using the -g flag to avoid the first panic, the time will be set and then the server will be inadvertently rate-limited and ignored until the local system catches up with the time as it was set before the negative jump. 

This is a bug in the ntp_monitor() code that needs to be resolved upstream. For the time being the workaround is to use ntpd in ntpdate mode (the `-q` option) before starting ntpd normally.

I will update this issue when I am able to create the bug upstream.

The fix for this will need to be backported to the 6 branch.

## Steps to reproduce


### Pre-set options

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/pkg/rtems-net-services/-/issues/12
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20250301/b2654e7c/attachment.htm>