No Idea - I've been using tlsdate ( https://github.com/ioerror/tlsdate )
inside my Cloud VM images recently to set initial time  as a lot of the
time ntp traffic is firewalled. Whereas there is generally a https source
you can reach from inside locked down networks.



On 15 September 2017 at 03:46, Rui Ribeiro <[email protected]> wrote:

> Hi,
>
> Does NTPDd supports "tinker panic 0" as the linux one?
>
> On 14 September 2017 at 12:46, Joel Wirāmu Pauling <[email protected]>
> wrote:
>
>> Run NTPd on the hypervisor and NTP client In VM. Run ntpdate at boot
>> before
>> starting NTPd on the client to ensure the stepping is not too far off
>> first.
>>
>> On 14 Sep. 2017 11:35 pm, "Aaron Marcher" <[email protected]> wrote:
>>
>> Hi all,
>>
>> I have a weird problem on my OpenBSD server. It is a virtualized guest
>> under QEMU-KVM. Apperently time management is completely off. With HPET
>> and
>> normal HW-clock the command "time sleep 1" shows a little bit more than a
>> second after a fresh boot. After a few hours the result is about 10
>> seconds. Additionally the clock drifts slowly. The problem is on OpenBSD
>> 6.1 with all syspatches applied.
>> Does anybody know how to fix the problem?
>> Thank you very much in advance!
>>
>> Regards,
>> Aaron Marcher
>>
>> --
>> Web: https://drkhsh.at/ or http://drkhsh5rv6pnahas.onion/
>> Gopher: gopher://drkhsh.at or gopher://drkhsh5rv6pnahas.onion
>> GPG: 0x09e71697435bf54b
>> Fingerprint: 57D2 5F2C 9402 A6BD FEF9 B3B6 09E7 1697 435B F54B
>>
>
>
>
> --
> Regards,
>
> --
> Rui Ribeiro
> Senior Linux Architect and Network Administrator
> ISCTE-IUL
> https://www.linkedin.com/pub/rui-ribeiro/16/ab8/434
>

Reply via email to