Cool, its fixed.
2014-08-13 21:08 GMT+02:00 Lennart Poettering :
> On Wed, 13.08.14 21:01, Daniel Buch ([email protected]) wrote:
>
> > Indeed, i run gnome and gnomes NetworkManager.
> >
> > I just tested the binary approach with LOG_LEVEL=debug (log attached
> below
> > and it worked, al
On Wed, 13.08.14 21:01, Daniel Buch ([email protected]) wrote:
> Indeed, i run gnome and gnomes NetworkManager.
>
> I just tested the binary approach with LOG_LEVEL=debug (log attached below
> and it worked, also systemctl start systemd-timesyncd.service works.
I think I fixed it now in g
Indeed, i run gnome and gnomes NetworkManager.
I just tested the binary approach with LOG_LEVEL=debug (log attached below
and it worked, also systemctl start systemd-timesyncd.service works.
Added new server time1.google.com.
Added new server time2.google.com.
Added new server time3.google.com.
A
On Wed, 13.08.14 20:35, Daniel Buch ([email protected]) wrote:
> With current git i noticed systemd-timesyncd failed and complain like this,
> log attached below.
>
> aug 13 20:12:08 dbuch-laptop systemd[1]: Starting Network Time
> Synchronization...
> aug 13 20:12:08 dbuch-laptop systemd[
With current git i noticed systemd-timesyncd failed and complain like this,
log attached below.
aug 13 20:12:08 dbuch-laptop systemd[1]: Starting Network Time
Synchronization...
aug 13 20:12:08 dbuch-laptop systemd[1]: systemd-timesyncd.service: main
process exited, code=exited, status=1/FAILURE
a
