Displaying 4 results from an estimated 4 matches for "time_server_".
2018 Nov 06
2
Time server on AD DC in an LXD container.
...rt
> the ntpsigndsocket option.
>
> @Marco - your response got me searching in another direction. I had tried
> ntpd in the container, which LXD did not like. My research turned up that
> Ubuntu now strongly favors chrony as of 18.04 AND that chrony has been
> patched to work as a time_server_ (which is what I need) in containers.
>
> I've successfully installed chrony in the container and have setup
> chrony.conf for ntpsigndsocket (and other suggested settings from
> https://wiki.samba.org/index.php/Time_Synchronisation. I've also
> verified/set ownership and per...
2018 Nov 05
4
Time server on AD DC in an LXD container.
After reading the instructions at
https://wiki.samba.org/index.php/Time_Synchronisation, I still have
questions about how samba interacts with nptd.
The issue is that LXD doesn't want containers setting the time and so won't
start ntpd at container startup even though it's enabled in systemd. The
host does sync it's time with a national time server, so we can assume that
the
2018 Nov 06
0
Fwd: Time server on AD DC in an LXD container.
...for this is too old to support
the ntpsigndsocket option.
@Marco - your response got me searching in another direction. I had tried
ntpd in the container, which LXD did not like. My research turned up that
Ubuntu now strongly favors chrony as of 18.04 AND that chrony has been
patched to work as a time_server_ (which is what I need) in containers.
I've successfully installed chrony in the container and have setup
chrony.conf for ntpsigndsocket (and other suggested settings from
https://wiki.samba.org/index.php/Time_Synchronisation. I've also
verified/set ownership and permissions for /var/lib/sa...
2018 Nov 07
0
Time server on AD DC in an LXD container.
...t option.
> >
> > @Marco - your response got me searching in another direction. I had tried
> > ntpd in the container, which LXD did not like. My research turned up that
> > Ubuntu now strongly favors chrony as of 18.04 AND that chrony has been
> > patched to work as a time_server_ (which is what I need) in containers.
> >
> > I've successfully installed chrony in the container and have setup
> > chrony.conf for ntpsigndsocket (and other suggested settings from
> > https://wiki.samba.org/index.php/Time_Synchronisation. I've also
> > verif...