6:09 p.m.
I have Fedora 22 Server Beta TC4 (I realize TC6 is current0 installed,
and just today realized the date+time is wrong by 20 hours. I don't
know why it would be this wrong absent something to keep it accurate,
however chrony is was not installed by default. It is installed by
default with Fedora 21 Server. So? Is this inadvertent? I think
something needs to keep the time correct.
--
Chris Murphy
3:59 p.m.
On Thu, 2015-04-02 at 17:09 -0600, Chris Murphy wrote:
I have Fedora 22 Server Beta TC4 (I realize TC6 is current0
installed,
and just today realized the date+time is wrong by 20 hours. I don't
know why it would be this wrong absent something to keep it accurate,
however chrony is was not installed by default. It is installed by
default with Fedora 21 Server. So? Is this inadvertent? I think
something needs to keep the time correct.
Good question. This did not happen intentionally as far as I am aware.
I'm looking into what happened.
4:45 p.m.
On Mon, 2015-04-06 at 16:59 -0400, Stephen Gallagher wrote:
On Thu, 2015-04-02 at 17:09 -0600, Chris Murphy wrote:
> I have Fedora 22 Server Beta TC4 (I realize TC6 is current0
> installed,
> and just today realized the date+time is wrong by 20 hours. I don't
> know why it would be this wrong absent something to keep it
> accurate,
> however chrony is was not installed by default. It is installed by
> default with Fedora 21 Server. So? Is this inadvertent? I think
> something needs to keep the time correct.
>
Good question. This did not happen intentionally as far as I am
aware.
I'm looking into what happened.
Maybe I'm reading things wrong, but it looks like chrony shouldn't
have been installed by default on F21 Server either (at least
technically). The fact that it was seems to have been a happy accident.
The only thing in F21 that could have pulled it in was a conditional
in @standard that says to pull in chrony if the "control-center"
package was also being installed.
Anyway, I've just pushed a comps update[1] to add chrony to the
@server-product group (a catch-all for things we want in the Server
defaults that don't clearly fit into the @server-hardware-support,
@headless-management, @container-management or @domain-client groups).
[1]
https://git.fedorahosted.org/cgit/comps.git/commit/?id=be00e397765f841ca6...
7:08 p.m.
On Mon, 2015-04-06 at 17:45 -0400, Stephen Gallagher wrote:
On Mon, 2015-04-06 at 16:59 -0400, Stephen Gallagher wrote:
> On Thu, 2015-04-02 at 17:09 -0600, Chris Murphy wrote:
> > I have Fedora 22 Server Beta TC4 (I realize TC6 is current0
> > installed,
> > and just today realized the date+time is wrong by 20 hours. I don't
> > know why it would be this wrong absent something to keep it
> > accurate,
> > however chrony is was not installed by default. It is installed by
> > default with Fedora 21 Server. So? Is this inadvertent? I think
> > something needs to keep the time correct.
> >
>
> Good question. This did not happen intentionally as far as I am
> aware.
> I'm looking into what happened.
Maybe I'm reading things wrong, but it looks like chrony shouldn't
have been installed by default on F21 Server either (at least
technically). The fact that it was seems to have been a happy accident.
The only thing in F21 that could have pulled it in was a conditional
in @standard that says to pull in chrony if the "control-center"
package was also being installed.
Anyway, I've just pushed a comps update[1] to add chrony to the
@server-product group (a catch-all for things we want in the Server
defaults that don't clearly fit into the @server-hardware-support,
@headless-management, @container-management or @domain-client groups).
[1]
https://git.fedorahosted.org/cgit/comps.git/commit/?id=be00e397765f841ca6...
Given the domain controller role uses ntpd, shouldn't we rather install
that one ?
Simo.
--
Simo Sorce * Red Hat, Inc * New York
3:01 a.m.
On Mon, Apr 06, 2015 at 08:08:43PM -0400, Simo Sorce wrote:
On Mon, 2015-04-06 at 17:45 -0400, Stephen Gallagher wrote:
> Anyway, I've just pushed a comps update[1] to add chrony to the
> @server-product group (a catch-all for things we want in the Server
> defaults that don't clearly fit into the @server-hardware-support,
> @headless-management, @container-management or @domain-client groups).
>
> [1]
>
https://git.fedorahosted.org/cgit/comps.git/commit/?id=be00e397765f841ca6...
Given the domain controller role uses ntpd, shouldn't we rather install
that one ?
Is that for the MS-SNTP authentication? Would there be any interest in
adding support for MS-SNTP to chronyd?
--
Miroslav Lichvar
7:18 a.m.
On Tue, 2015-04-07 at 10:01 +0200, Miroslav Lichvar wrote:
On Mon, Apr 06, 2015 at 08:08:43PM -0400, Simo Sorce wrote:
> On Mon, 2015-04-06 at 17:45 -0400, Stephen Gallagher wrote:
> > Anyway, I've just pushed a comps update[1] to add chrony to the
> > @server-product group (a catch-all for things we want in the Server
> > defaults that don't clearly fit into the @server-hardware-support,
> > @headless-management, @container-management or @domain-client groups).
> >
> > [1]
> >
https://git.fedorahosted.org/cgit/comps.git/commit/?id=be00e397765f841ca6...
>
> Given the domain controller role uses ntpd, shouldn't we rather install
> that one ?
Is that for the MS-SNTP authentication?
No, we do not make use of that yet (we probably should).
We used ntpd because it was the only one able to serve as a time server,
has cronyd gained the ability to be a server itself ?
Would there be any interest in adding support for MS-SNTP to chronyd?
It would probably be a good thing, I know samba has hooks for that on
the server side at least.
Simo.
--
Simo Sorce * Red Hat, Inc * New York
7:37 a.m.
On Tue, Apr 07, 2015 at 08:18:47AM -0400, Simo Sorce wrote:
On Tue, 2015-04-07 at 10:01 +0200, Miroslav Lichvar wrote:
> On Mon, Apr 06, 2015 at 08:08:43PM -0400, Simo Sorce wrote:
> > Given the domain controller role uses ntpd, shouldn't we rather install
> > that one ?
>
> Is that for the MS-SNTP authentication?
No, we do not make use of that yet (we probably should).
We used ntpd because it was the only one able to serve as a time server,
has cronyd gained the ability to be a server itself ?
chronyd can work as an NTP server, but unlike ntpd it's disabled by
default. The allow directive can be used in chrony.conf or at runtime
with "chronyc -a allow" to allow NTP client access.
> Would there be any interest in adding support for MS-SNTP to
chronyd?
It would probably be a good thing, I know samba has hooks for that on
the server side at least.
Yes, that's what I meant, support for the samba ntp signd socket. With
chronyd I think the default would be disabled and it would need to be
enabled in chrony.conf when needed.
Maybe chronyd should include files from an /etc/chrony.d directory
where other packages could put their files to enable NTP access, etc?
--
Miroslav Lichvar
8:44 a.m.
On Tue, 2015-04-07 at 14:37 +0200, Miroslav Lichvar wrote:
On Tue, Apr 07, 2015 at 08:18:47AM -0400, Simo Sorce wrote:
> On Tue, 2015-04-07 at 10:01 +0200, Miroslav Lichvar wrote:
> > On Mon, Apr 06, 2015 at 08:08:43PM -0400, Simo Sorce wrote:
> > > Given the domain controller role uses ntpd, shouldn't we rather
install
> > > that one ?
> >
> > Is that for the MS-SNTP authentication?
>
> No, we do not make use of that yet (we probably should).
> We used ntpd because it was the only one able to serve as a time server,
> has cronyd gained the ability to be a server itself ?
chronyd can work as an NTP server, but unlike ntpd it's disabled by
default. The allow directive can be used in chrony.conf or at runtime
with "chronyc -a allow" to allow NTP client access.
> > Would there be any interest in adding support for MS-SNTP to chronyd?
>
> It would probably be a good thing, I know samba has hooks for that on
> the server side at least.
Yes, that's what I meant, support for the samba ntp signd socket. With
chronyd I think the default would be disabled and it would need to be
enabled in chrony.conf when needed.
Maybe chronyd should include files from an /etc/chrony.d directory
where other packages could put their files to enable NTP access, etc?
Yeah a /etc/chrony.d directory where you can drop config files would
probably be nice too. (Hopefully we do not end up dropping conflicting
directives :-)
Simo.
--
Simo Sorce * Red Hat, Inc * New York
7:40 a.m.
On Tue, Apr 07, 2015 at 08:18:47AM -0400, Simo Sorce wrote:
On Tue, 2015-04-07 at 10:01 +0200, Miroslav Lichvar wrote:
> On Mon, Apr 06, 2015 at 08:08:43PM -0400, Simo Sorce wrote:
> > On Mon, 2015-04-06 at 17:45 -0400, Stephen Gallagher wrote:
> > > Anyway, I've just pushed a comps update[1] to add chrony to the
> > > @server-product group (a catch-all for things we want in the Server
> > > defaults that don't clearly fit into the @server-hardware-support,
> > > @headless-management, @container-management or @domain-client groups).
> > >
> > > [1]
> > >
https://git.fedorahosted.org/cgit/comps.git/commit/?id=be00e397765f841ca6...
> >
> > Given the domain controller role uses ntpd, shouldn't we rather install
> > that one ?
>
> Is that for the MS-SNTP authentication?
No, we do not make use of that yet (we probably should).
We used ntpd because it was the only one able to serve as a time server,
has cronyd gained the ability to be a server itself ?
Chronyd has always had ability to act as a NTP server. Do you mean some
specific functionality?
--
Tomasz Torcz Morality must always be based on practicality.
xmpp: zdzichubg(a)chrome.pl -- Baron Vladimir Harkonnen
7:30 a.m.
On Mon, 2015-04-06 at 20:08 -0400, Simo Sorce wrote:
On Mon, 2015-04-06 at 17:45 -0400, Stephen Gallagher wrote:
> On Mon, 2015-04-06 at 16:59 -0400, Stephen Gallagher wrote:
> > On Thu, 2015-04-02 at 17:09 -0600, Chris Murphy wrote:
> > > I have Fedora 22 Server Beta TC4 (I realize TC6 is current0
> > > installed,
> > > and just today realized the date+time is wrong by 20 hours. I
> > > don't
> > > know why it would be this wrong absent something to keep it
> > > accurate,
> > > however chrony is was not installed by default. It is
> > > installed by
> > > default with Fedora 21 Server. So? Is this inadvertent? I think
> > > something needs to keep the time correct.
> > >
> >
> > Good question. This did not happen intentionally as far as I am
> > aware.
> > I'm looking into what happened.
>
>
> Maybe I'm reading things wrong, but it looks like chrony shouldn't
> have been installed by default on F21 Server either (at least
> technically). The fact that it was seems to have been a happy
> accident.
>
> The only thing in F21 that could have pulled it in was a
> conditional
> in @standard that says to pull in chrony if the "control-center"
> package was also being installed.
>
> Anyway, I've just pushed a comps update[1] to add chrony to the
> @server-product group (a catch-all for things we want in the
> Server
> defaults that don't clearly fit into the @server-hardware-support,
> @headless-management, @container-management or @domain-client
> groups).
>
> [1]
>
https://git.fedorahosted.org/cgit/comps.git/commit/?id=be00e397765f841ca6...
Given the domain controller role uses ntpd, shouldn't we rather
install
that one ?
I need to retest, but I think installing the domain controller role
will automatically remove chrony and replace it with ntpd, so that's
probably not an issue.
The main reason I'm sticking with chrony for now is because the
necessary hooks are already in place. If the chronyd package is
installed, it's automatically started by the systemd presets and
integrated with systemd-timesyncd. If we want to move to ntpd, we'll
need to address those same integration points.
3304
days inactive
3309
days old
server@lists.fedoraproject.org
9 comments
5 participants
participants (5)
-
Chris Murphy -
Miroslav Lichvar -
Simo Sorce -
Stephen Gallagher -
Tomasz Torcz