Anonymous | Login | 2024-11-21 01:31 MST |
Main | My View | View Issues | Change Log | Roadmap | Repositories |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0019591 | ClearOS | app-date - Date and Time | public | 2018-03-29 10:57 | 2018-04-03 12:32 | ||||
Reporter | user2 | ||||||||
Assigned To | user2 | ||||||||
Priority | normal | Severity | minor | Reproducibility | have not tried | ||||
Status | closed | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | 7.4.0 | ||||||||
Target Version | 7.4.0 Updates | Fixed in Version | 7.4.0 Updates | ||||||
Summary | 0019591: Merge NTP Time synchronization with timesync | ||||||||
Description | The NTP_Time.synchronize() API call should use the logic defined in timesync. Notably, the "ntpdate" command should not be used when an NTP server is running. | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
Notes | |
(0007371) user2 2018-04-03 12:32 |
On review, this is change would have some downside. If the clock skew is too far off (e.g. a BIOS clock reset), then the "ntpd -q" command will refuse to update the clock. With NTP getting deprecated in ClearOS 8, we'll leave it as is for ClearOS 7. |