NTP?

[Niels Kobschätzki]

I booted my computer tonight and the time was off by 2 hours. Then I figured out
that ntp is not running. So I installed ntpdate and of course it cannot use any
pre-configured time-servers. Are there any time servers that dom0 can use? Or
which documentation would I need to read to give dom0 access to a couple of time
servers?
Or is ntp problematic enough that dom0 shouldn't use it at all cost?

Niels

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

The time should be synced automatically by this cron job (in dom0):

/etc/cron.d/qubes-sync-clock.cron

...which uses the qvm-sync-clock command.

Check your cron log to see if it's been running:

$ cat /var/log/cron

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXitymAAoJENtN07w5UDAwwdoP/1+dovvJPZhG2ZeIhZ1vFfYj
8ZgBvFKGA/0HG0EIo9yApTnPFXUaV4K4IxXy/FyjCcii8854zhqIWhH6YuZ0Cr2L
I4ToA/1VgMSYOXdwMxNwvds/i6+4kd8oA7LCRUlktqQq0swtAMNqwle2PDEhf5p8
rGB2gzadh8ckPSrDDi0FR7oxraz+dq1kE27KO/iKfmG0eFMWinVG+ifSl+1Y3qwB
b+qbMZiomR5caHD/I0+ph/WSQC2UAUJvkUkceomjIVHNZVgKMqd+PUMr9jisJjfi
1QbI1beja0nHuv9e0f7KAsgMej8491jPZHZ9RgEK00G/cejd0VC3XFRV53P6F0T+
W0O4J9eP9vbni4bN/Lin8oH4kFQuIXV4kIiLIU7hfSgnBdIeecItU9qxmKzh5dd1
mOXisvW6rVyE1LsIu8ZhvC55QqpEKWlrjQNKnBK/cWodDAfDtwGvVLr30Vj8ARfW
LFMBcwwfp1pW2HZqhIfh80B4xOJUTBP8IAVgTC19goN998XRmFIMiazNeVVkvNf6
OmncECqKpOWeO7SwADmbRPDifU5FPoOfER54y4F+VwaXUT7cZZh174UMMyK18nWV
Dkh7uHNOUSikh3+iIt92ntRzLgHtJmg8N4c2Pu4xQDRS7zvXC0W6uwKQpoO4p7AC
cMo5+8QZbBwHlRP821t+
=SaFk
-----END PGP SIGNATURE-----

[Niels Kobschätzki]

Andrew David Wong writes:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On 2016-07-16 14:06, Niels Kobschätzki wrote:
>>
>> I booted my computer tonight and the time was off by 2 hours. Then I
>> figured out that ntp is not running. So I installed ntpdate and of course
>> it cannot use any pre-configured time-servers. Are there any time servers
>> that dom0 can use? Or which documentation would I need to read to give
>> dom0 access to a couple of time servers? Or is ntp problematic enough that
>> dom0 shouldn't use it at all cost?
>>
>> Niels
>>
>
> The time should be synced automatically by this cron job (in dom0):
>
> /etc/cron.d/qubes-sync-clock.cron
>
> ...which uses the qvm-sync-clock command.

Ah, good to know. Thanks.

> Check your cron log to see if it's been running:
>
> $ cat /var/log/cron

That file doesn't exist.

Niels

[Niels Kobschätzki]

Andrew David Wong writes:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On 2016-07-16 14:06, Niels Kobschätzki wrote:
>>
>> I booted my computer tonight and the time was off by 2 hours. Then I
>> figured out that ntp is not running. So I installed ntpdate and of course
>> it cannot use any pre-configured time-servers. Are there any time servers
>> that dom0 can use? Or which documentation would I need to read to give
>> dom0 access to a couple of time servers? Or is ntp problematic enough that
>> dom0 shouldn't use it at all cost?
>>

> The time should be synced automatically by this cron job (in dom0):
>
> /etc/cron.d/qubes-sync-clock.cron
>
> ...which uses the qvm-sync-clock command.
>
> Check your cron log to see if it's been running:
>
> $ cat /var/log/cron

But systemctl status crond shows that it apparently runs.
Did anyone think about switching from cron to systemd-timers for QubesOS? If yes
but didn't do the switch, I'd be interested in hearing why. Personally I really prefer them

Niels

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016-07-16 22:04, Niels Kobschätzki wrote:
>> $ cat /var/log/cron
>
> That file doesn't exist.
>

If you're on Fedora 23 in dom0 (R3.2-rc1), then I guess there was some change
since Fedora 20.

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXi28cAAoJENtN07w5UDAwS3kP/0bVtUUYzA5JcO3cfzkl+23X
n3h8A7q2/0x3dbABLZv5eCMIibsK5TyTF2IoAFD7jAeC7vlaub22WKlNUboKPHqj
lVSYpBhezwoZCKecHnvh1lptWl3HU4tQnSVWSXf4BVQN12aQ53aNKRx+o8Wf7p0/
BtCIhV6ekyafStX7lQoqtLg9yBaDDpiKuhdWaYgDFnGsL59d0U4rN1FGL97W1+/R
hF8fj6W+0+oQYZTGOR6RnnTEaQLmujYBjjlgFpTC1Qxh6ev147CLVQiP2YDxvsIc
OY4jrmbImeb0lujBxXWacTiYnT6U6BRfEVt02hi4wZFV2+FNyMFrFu4JosH2g3JB
54Lx19GSTO3IEXOOJbszgaVaywbZ/c75VtSzuew6Nr9c6bxIakB52WsbiftTxotO
APjPker5Dhq+9+ot4DxZ5sy5zKx618k51EoATVTqh/QniXhF6MAHlyTofmMEbbRF
9uIn/thJDCRIgQ4VyL20Cna/C1bnpnEJyg9qeiu4SQI7uiZzua6pTsDxwAbeQOBA
da/8fq6oKlSZYU3Wq3zvsDXW5hsmBWhZm+dHVQtlTp4qxN8XbcmTIPZ94b6rWgZu
nBglWi4U5DeIUghSvPMokOwXTt/ovZliLWWiqZYzMsM5l5E+cacqfM5Cyo9W5oZZ
hVlnWx5Sj0YYkmjTB+cx
=Nrgw
-----END PGP SIGNATURE-----

[Niels Kobschätzki]

Andrew David Wong writes:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On 2016-07-16 22:04, Niels Kobschätzki wrote:
>>> $ cat /var/log/cron
>>
>> That file doesn't exist.
>>
>
> If you're on Fedora 23 in dom0 (R3.2-rc1), then I guess there was some change
> since Fedora 20.

That's the reason then probably.

Niels