Enable ntpd daemon#1287
Conversation
I am using docker-machines as nodes in our Jenkins CI, I noticed that the machines time keeps drifting, After digging into your code, I noticed that the `rc.d/ntpd` sets the Do Not Demonize flag `-n`. After a week or so of monitoring, the time sync seems to be working. Was there a reason for this flag? If not, is this a possible fix?
|
We use |
|
Thank you for your valuable input. I did see the If you believe this is still not related. any ideas why ntpd wasnt working before and now it does? I have read about this issue in many places before without a clear solution. I would also argue that ntpd should be demonized and the log file is set in the config. I am simply questioning whether u should sacrifice demonizing for a log. Have a nice day :) |
|
We've had a lot of recurring issues with time synchronization in boot2docker. I imagine that your change working better is simply a red-herring -- given enough time, I'd guess that it'd start to exhibit the same issues as the current code, since it functionally isn't any different (except that logs don't go into the same file). |
|
Hello, |
|
Also to set the logfile, a |
Nope, not at all -- there is literally no difference at all. One way, the daemon starts in the background. The other way, the daemon starts in the background. Both ways, if the daemon dies, the daemon dies. Does Busybox's |
|
I gave it a try and unfortunately no :( |
2 participants
I am using docker-machines as nodes in our Jenkins CI, I noticed that the machines time keeps drifting, After digging into your code, I noticed that the
rc.d/ntpdsets the Do Not Demonize flag-n. After a week or so of monitoring, the time sync seems to be working.Was there a reason for this flag? If not, is this a possible fix?