unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: Adam Mazurkiewicz <trzczy@gmail.com>, help-guix@gnu.org
Subject: Re: Using an ntp service
Date: Wed, 22 May 2019 17:31:45 +0200	[thread overview]
Message-ID: <87blzu7bfi.fsf@roquette.mug.biscuolo.net> (raw)
In-Reply-To: <CALStFoF=C-zYZNR+2Kd0nz0Py7nbWkZ1L6WsgHJccCU3VkQrQw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]

Hi Adam,

Adam Mazurkiewicz <trzczy@gmail.com> writes:

[...]

> I expected that it would sync system time, but it did not. I have
> still been getting the time of my computer BIOS in a terminal, not the
> synced one.

If system clock is too late (or too far in the future) ntpd will not
update it 

«Normally, ntpd exits if the offset exceeds the sanity limit, which is
1000 s by default. » [1] 

Is this your case?

> Also in Xfce DE Clock. I have no idea how to debug it and
> fix.

To debug you should check "sudo tac /var/log/messages | grep ntpd |
less" messages

> Any help will be appreciated.

Set your clock (via date command or some GUI) and then "sudo hwclock
--systohc" to update your BIOS clock.

Last but not least: check your hardware clock setting are preserved
between reboots, if not you should change it's battery (if it's not
broken).

HTH! Gio'


[1] http://doc.ntp.org/4.1.0/ntpd.htm


-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2019-05-22 15:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22 13:30 Using an ntp service Adam Mazurkiewicz
2019-05-22 15:31 ` Giovanni Biscuolo [this message]
     [not found]   ` <CALStFoH1uU1SQ=K34fMKGxqAVhuCp=1_f3dGzJJ6h6x0=KGayA@mail.gmail.com>
2019-05-24 17:19     ` Adam Mazurkiewicz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87blzu7bfi.fsf@roquette.mug.biscuolo.net \
    --to=g@xelera.eu \
    --cc=help-guix@gnu.org \
    --cc=trzczy@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).