Dennis Wicks w...@mgssub.com writes:
Mart van de Wege wrote on 07/27/2015 12:49 AM:
Gary Dale garyd...@torfree.net writes:
On 26/07/15 02:44 PM, Mart van de Wege wrote:
Gary Dale garyd...@torfree.net writes:
Upgrading to sid is asking for trouble. Sid isn't called unstable for
nothing.
Mart van de Wege wrote on 07/27/2015 12:49 AM:
Gary Dale garyd...@torfree.net writes:
On 26/07/15 02:44 PM, Mart van de Wege wrote:
Gary Dale garyd...@torfree.net writes:
Upgrading to sid is asking for trouble. Sid isn't called unstable for
nothing.
I know. I really do. I only have been
Renaud (Ron) OLGIATI wrote on 07/26/2015 03:40 PM:
On Sun, 26 Jul 2015 15:27:50 -0500
John Hasler jhas...@newsguy.com wrote:
I want to be able to set the time if for some reason the clock is
completely incorrect (this occurred from time to time in the past).
Use your wristwatch.
Or better,
Gary Dale garyd...@torfree.net writes:
On 26/07/15 02:44 PM, Mart van de Wege wrote:
Gary Dale garyd...@torfree.net writes:
Upgrading to sid is asking for trouble. Sid isn't called unstable for
nothing.
I know. I really do. I only have been running Debian since potato. On
the other hand,
On 2015-07-26 02:31:45 +0200, Michael Biebl wrote:
You can have a client, which is a daemon.
ntp implements both, an NTP client and server.
systemd-timesyncd only implements a client (running as daemon).
chrony, fwiw, is another client (running as daemon).
ntpdate is a client (triggered via
On Sunday 26 July 2015 13:17:02 Renaud OLGIATI wrote:
On Sun, 26 Jul 2015 10:54:35 +0100
Lisi Reisz lisi.re...@gmail.com wrote:
But that is for wheezy and earlier. systemd is, of course, different.
Maybe the list should implement a rule, that people asking a question tell
us whether they
On 2015-07-26 07:53:45 -0500, John Hasler wrote:
Vincent Lefevre writes:
Unfortunately none of them is secure, I mean: some attacker won't tend
to make the date on your machine incorrect because of lack of
authentication.
http://www.ntp.org/ntpfaq/NTP-s-config-adv.htm
See section
On Sun 26 Jul 2015 at 14:57:02 +0200, Sven Hartge wrote:
Michael Biebl bi...@debian.org wrote:
The assumption here is, that if the admin explicitly installed ntp, it
should be preferred of systemd-timesyncd.
See
Am 26.07.2015 um 15:39 schrieb Vincent Lefevre:
On 2015-07-26 14:25:20 +0100, Brian wrote:
On Sun 26 Jul 2015 at 13:59:02 +0100, Lisi Reisz wrote:
On Sunday 26 July 2015 13:38:45 Michael Biebl wrote:
Yes. You actually need to do that. As long as ntp is installed,
systemd-timesyncd won't
Systemd-timesyncd is not a replacement for Ntpd or Chrony. It is just
an SNTP client similar to that used by Microsoft. It queries a single
server and does no error checking or authentication. Basically, it
replaces a cron job running Ntpdate.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI
REPLACE approx with chrony in the following;
Also years ago, and still today, there is approx which does a much
more sophisticated analysis of the data stream of repeated queries of
an ntp server. In addition to setting the local clock to the
same time as the external reference clock as is
On Sun, Jul 26, 2015 at 10:54:35AM +0100, Lisi Reisz wrote:
On Sunday 26 July 2015 05:09:37 CaT wrote:
On Sat, Jul 25, 2015 at 11:32:53PM -0400, Gene Heskett wrote:
It is, once ntpdate has slammed the correct time into the system at boot
time, then ntp takes over.
Unless I
On Sun, Jul 26, 2015 at 02:03:48AM +0200, Michael Biebl wrote:
Am 25.07.2015 um 21:26 schrieb Holger Schramm:
Am 25.07.2015 um 20:52 schrieb John J. Boyer:
I am wondering if my Jessie system is updating its clock regularly. It
gives a
different time than my Windows box. What package
On Sun, 26 Jul 2015 10:54:35 +0100
Lisi Reisz lisi.re...@gmail.com wrote:
But that is for wheezy and earlier. systemd is, of course, different.
Maybe the list should implement a rule, that people asking a question tell us
whether they are running systemd or not.
Given that the advent of
Am 26.07.2015 um 13:44 schrieb Chris Bannister:
On Sun, Jul 26, 2015 at 02:03:48AM +0200, Michael Biebl wrote:
Am 25.07.2015 um 21:26 schrieb Holger Schramm:
Am 25.07.2015 um 20:52 schrieb John J. Boyer:
I am wondering if my Jessie system is updating its clock regularly. It
gives a
On Sunday 26 July 2015 15:14:03 Michael Biebl wrote:
Am 26.07.2015 um 14:57 schrieb Lisi Reisz:
Yes, on my one systemd box, I had a problem with which no-one could help
me.
I do not allege that systemd directly caused it, but that the advent of
systemd caused a lot that had worked one
It may have been an X-Y question, but the answer to the question
actually asked, was ntp.
That is *an* answer. The full answer is that the Chrony and Ntp
packages provide time daemons. Systemd-timesyncd provides an SNTP
client which is probably adequate for most users.
--
John Hasler
Sven Hartge s...@svenhartge.de wrote:
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
That one is not present in Sid.
Ah, -ENOCOFFEE, I meant of course That one is not present in Jessie.
S°
--
Sigmentation fault. Core dumped.
--
To UNSUBSCRIBE, email to
anxiousmac writes:
Years ago ... we didn't all have always-on connections.
Chrony was developed to solve that problem.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Sun 26 Jul 2015 at 15:39:48 +0200, Vincent Lefevre wrote:
On 2015-07-26 14:25:20 +0100, Brian wrote:
On Sun 26 Jul 2015 at 13:59:02 +0100, Lisi Reisz wrote:
On Sunday 26 July 2015 13:38:45 Michael Biebl wrote:
Yes. You actually need to do that. As long as ntp is installed,
On Sun, Jul 26, 2015 at 02:38:45PM +0200, Michael Biebl wrote:
Am 26.07.2015 um 13:44 schrieb Chris Bannister:
On Sun, Jul 26, 2015 at 02:03:48AM +0200, Michael Biebl wrote:
If you are using systemd, look for timedatectl. Settings are at
/etc/systemd/timesyncd.conf
In most cases,
On Sun 26 Jul 2015 at 13:59:02 +0100, Lisi Reisz wrote:
On Sunday 26 July 2015 13:38:45 Michael Biebl wrote:
Yes. You actually need to do that. As long as ntp is installed,
systemd-timesyncd won't start.
The assumption here is, that if the admin explicitly installed ntp, it
should be
On Sun, 26 Jul 2015, Michael Biebl wrote:
Yes. You actually need to do that. As long as ntp is
installed, systemd-timesyncd won't start.
I'd like to suggest that if I were a vindictive,
morally shallow person I would be rushing back into
this thread to point out: Oh look! Another reason why
On Sunday 26 July 2015 14:52:56 Bob Bernstein wrote:
Another reason why
the correct answer to the OP's question is NOT ntp.
The question was:
What package contains the time daemon?
It may have been an X-Y question, but the answer to the question actually
asked, was ntp.
Lisi
Michael Biebl bi...@debian.org wrote:
Am 26.07.2015 um 13:44 schrieb Chris Bannister:
On Sun, Jul 26, 2015 at 02:03:48AM +0200, Michael Biebl wrote:
Am 25.07.2015 um 21:26 schrieb Holger Schramm:
Am 25.07.2015 um 20:52 schrieb John J. Boyer:
I am wondering if my Jessie system is updating its
On Sunday 26 July 2015 13:38:45 Michael Biebl wrote:
Am 26.07.2015 um 13:44 schrieb Chris Bannister:
On Sun, Jul 26, 2015 at 02:03:48AM +0200, Michael Biebl wrote:
Am 25.07.2015 um 21:26 schrieb Holger Schramm:
Am 25.07.2015 um 20:52 schrieb John J. Boyer:
I am wondering if my Jessie
Am 26.07.2015 um 14:57 schrieb Lisi Reisz:
Yes, on my one systemd box, I had a problem with which no-one could help me.
I do not allege that systemd directly caused it, but that the advent of
systemd caused a lot that had worked one way before, to have to work
differently now; that there
L'octidi 8 thermidor, an CCXXIII, Paul E Condon a écrit :
Also years ago, and still today, there is chrony which does a much
more sophisticated analysis of the data stream of repeated queries of
an ntp server. In addition to setting the local clock to the
same time as the external reference
Paul E Condon writes:
Also years ago, and still today, there is approx which does a much
more sophisticated analysis of the data stream of repeated queries of
an ntp server. In addition to setting the local clock to the same time
as the external reference clock as is done by both ntp and
On Sunday, 26 July 2015 05:30:04 UTC+1, CaT wrote:
On Sat, Jul 25, 2015 at 11:32:53PM -0400, Gene Heskett wrote:
It is, once ntpdate has slammed the correct time into the system at boot
time, then ntp takes over.
Unless I misremember, you don't even need ntpdate. Starting ntp with
-g
Vincent Lefevre writes:
Unfortunately none of them is secure, I mean: some attacker won't tend
to make the date on your machine incorrect because of lack of
authentication.
http://www.ntp.org/ntpfaq/NTP-s-config-adv.htm
See section 6.6.2, Authentication
Even without it, though, sucessfully
On 2015-07-26 14:25:20 +0100, Brian wrote:
On Sun 26 Jul 2015 at 13:59:02 +0100, Lisi Reisz wrote:
On Sunday 26 July 2015 13:38:45 Michael Biebl wrote:
Yes. You actually need to do that. As long as ntp is installed,
systemd-timesyncd won't start.
The assumption here is, that if the
I wrote:
http://www.ntp.org/ntpfaq/NTP-s-config-adv.htm
See section 6.6.2, Authentication
Vincent Lefevre writes:
I don't see how this can work with public NTP servers!
If you need authentication you need to use trusted servers.
http://www.nist.gov/pml/div688/grp40/auth-ntp.cfm
Vincent Lefevre writes:
I want to be able to set the time if for some reason the clock is
completely incorrect (this occurred from time to time in the past).
Use your wristwatch.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
--
To UNSUBSCRIBE, email to
Paul E Condon wrote on 07/26/2015 10:14 AM:
On 20150726_0252-0700, anxious...@gmail.com wrote:
Also years ago, and still today, there is approx which does a much
more sophisticated analysis of the data stream of repeated queries of
an ntp server. In addition to setting the local clock to the
On 26/07/15 08:57 AM, Lisi Reisz wrote:
On Sunday 26 July 2015 13:17:02 Renaud OLGIATI wrote:
On Sun, 26 Jul 2015 10:54:35 +0100
Lisi Reisz lisi.re...@gmail.com wrote:
But that is for wheezy and earlier. systemd is, of course, different.
Maybe the list should implement a rule, that people
On 2015-07-26 15:27:50 -0500, John Hasler wrote:
Vincent Lefevre writes:
I want to be able to set the time if for some reason the clock is
completely incorrect (this occurred from time to time in the past).
Use your wristwatch.
This may be too late. The machine doesn't warn when the date
On 2015-07-26 10:06:05 -0500, John Hasler wrote:
I wrote:
http://www.ntp.org/ntpfaq/NTP-s-config-adv.htm
See section 6.6.2, Authentication
Vincent Lefevre writes:
I don't see how this can work with public NTP servers!
Actually there's another authentication system: Autokey, which is
On Sun, 26 Jul 2015 15:27:50 -0500
John Hasler jhas...@newsguy.com wrote:
I want to be able to set the time if for some reason the clock is
completely incorrect (this occurred from time to time in the past).
Use your wristwatch.
Or better, your cellphone or GPS receiver.
Cheers,
On Sunday 26 July 2015 05:09:37 CaT wrote:
On Sat, Jul 25, 2015 at 11:32:53PM -0400, Gene Heskett wrote:
It is, once ntpdate has slammed the correct time into the system at boot
time, then ntp takes over.
Unless I misremember, you don't even need ntpdate. Starting ntp with
-g will do just
CaT writes:
Unless I misremember, you don't even need ntpdate. Starting ntp with
-g will do just fine (and it's the default config - I add -N). I don't
even have ntpdate installed.
Yes. Ntpdate is obsolete.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
--
To UNSUBSCRIBE, email to
On 20150726_0252-0700, anxious...@gmail.com wrote:
On Sunday, 26 July 2015 05:30:04 UTC+1, CaT wrote:
On Sat, Jul 25, 2015 at 11:32:53PM -0400, Gene Heskett wrote:
It is, once ntpdate has slammed the correct time into the system at boot
time, then ntp takes over.
Unless I
On 26/07/15 10:45 AM, John Hasler wrote:
It may have been an X-Y question, but the answer to the question
actually asked, was ntp.
That is *an* answer. The full answer is that the Chrony and Ntp
packages provide time daemons. Systemd-timesyncd provides an SNTP
client which is probably
On 26/07/15 12:47 PM, Dennis Wicks wrote:
Paul E Condon wrote on 07/26/2015 10:14 AM:
On 20150726_0252-0700, anxious...@gmail.com wrote:
Also years ago, and still today, there is approx which does a much
more sophisticated analysis of the data stream of repeated queries of
an ntp server. In
Gary Dale garyd...@torfree.net writes:
I haven't had any significant problems with systemd but then I waited
several months before upgrading my servers to jessie and before
upgrading my workstation to stretch. Maybe it's because of MS-DO but
I've learned to wait for the .1 release before
On 2015-07-26 14:45:57 +0100, Brian wrote:
On Sun 26 Jul 2015 at 15:39:48 +0200, Vincent Lefevre wrote:
IMHO, it is bad to be forced to uninstall a package just to make
some other package work.
Like not being able to have postfix/exim4 and cups/lprng on a machine at
the same time, you
On Sun, 26 Jul 2015, Lisi Reisz wrote:
The question was:
What package contains the time daemon?
It may have been an X-Y question, but the answer to
the question actually asked, was ntp.
You are (again) stunningly correct Lisi. I don't seem
to have been able to stay focussed
On Sun, 26 Jul 2015, Gary Dale wrote:
Much of this discussion reminds me of an old Monty
Python skit ending with the line Lucky we didn't
say anything about the dirty knife. :)
I don't recall that bit, but then NO ONE EXPECTS THE
SPANISH INQUISITION!
Recently I checked out the price of
On 07/26/2015 at 08:51 PM, Chris Bannister wrote:
On Sun, Jul 26, 2015 at 12:02:07PM -0400, Gary Dale wrote:
Much of this discussion reminds me of an old Monty Python skit
ending with the line Lucky we didn't say anything about the dirty
knife. :)
IIRC, it was a dirty fork.
No - they
On Sun, Jul 26, 2015 at 09:34:46PM -0400, The Wanderer wrote:
On 07/26/2015 at 08:51 PM, Chris Bannister wrote:
On Sun, Jul 26, 2015 at 12:02:07PM -0400, Gary Dale wrote:
Much of this discussion reminds me of an old Monty Python skit
ending with the line Lucky we didn't say anything
On 26/07/15 02:44 PM, Mart van de Wege wrote:
Gary Dale garyd...@torfree.net writes:
I haven't had any significant problems with systemd but then I waited
several months before upgrading my servers to jessie and before
upgrading my workstation to stretch. Maybe it's because of MS-DO but
I've
John Hasler wrote:
The Wanderer writes:
The original question was What package contains the daemon that
updates the time from a central site?.
The ntp package contains such a daemon - indeed, until systemd, almost
certainly the primary such daemon.
The chrony package provides a time daemon
On Sun, Jul 26, 2015 at 12:02:07PM -0400, Gary Dale wrote:
On 26/07/15 10:45 AM, John Hasler wrote:
It may have been an X-Y question, but the answer to the question
actually asked, was ntp.
That is *an* answer. The full answer is that the Chrony and Ntp
packages provide time daemons.
On Sun, 26 Jul 2015, John Hasler wrote:
Systemd-timesyncd is not a replacement for Ntpd or
Chrony. It is just an SNTP client similar to that
used by Microsoft. It queries a single server and
does no error checking or authentication.
Basically, it replaces a cron job running Ntpdate.
A
On Saturday 25 July 2015 20:08:34 Bob Bernstein wrote:
On Sun, 26 Jul 2015, Iain M Conochie wrote:
No. This is an incorrect response.
Really?
Um...your own homework, below, suggests that ntp is
not the only package that performs the task in
question. Since ntpdate does not depend on
On Sat, Jul 25, 2015 at 11:32:53PM -0400, Gene Heskett wrote:
It is, once ntpdate has slammed the correct time into the system at boot
time, then ntp takes over.
Unless I misremember, you don't even need ntpdate. Starting ntp with
-g will do just fine (and it's the default config - I add -N).
On Sat, 25 Jul 2015, Gary Dale wrote:
ntp
No. This is an incorrect response.
--
I am not a loony. Why should I be tarred with the epithet
'loony' merely because I have a pet halibut? I've heard
tell that Sir Gerald Nabarro has a pet prawn called Simon
- you wouldn't call him a loony!
--
On 26/07/15 00:08, Bob Bernstein wrote:
On Sat, 25 Jul 2015, Gary Dale wrote:
ntp
No. This is an incorrect response.
Really?
apt-cache search ntp | grep ^ntp
ntp - Network Time Protocol daemon and utility programs
ntp-doc - Network Time Protocol documentation
ntpdate - client for
On Sat, 25 Jul 2015 19:08:33 -0400 (EDT)
Bob Bernstein poo...@ruptured-duck.com wrote:
On Sat, 25 Jul 2015, Gary Dale wrote:
ntp
No. This is an incorrect response.
According to the Description of the package ntp:
This package contains the NTP daemon and utility programs.
Cheers,
Ron.
I am wondering if my Jessie system is updating its clock regularly. It
gives a
different time than my Windows box. What package contains the daemon
that updates the time from a central site?
Thanks,
John
--
John J. Boyer; President,
AbilitiesSoft, Inc.
http://www.abilitiessoft.org
Madison,
On Sat 25 Jul 2015 at 13:52:28 -0500, John J. Boyer wrote:
I am wondering if my Jessie system is updating its clock regularly. It
gives a different time than my Windows box. What package contains the
daemon that updates the time from a central site?
You might want to quantify this time
Am 25.07.2015 um 20:52 schrieb John J. Boyer:
I am wondering if my Jessie system is updating its clock regularly. It
gives a
different time than my Windows box. What package contains the daemon
that updates the time from a central site?
If you are using systemd, look for timedatectl.
On 25/07/15 02:52 PM, John J. Boyer wrote:
I am wondering if my Jessie system is updating its clock regularly. It
gives a
different time than my Windows box. What package contains the daemon
that updates the time from a central site?
Thanks,
John
ntp
--
To UNSUBSCRIBE, email to
On 07/25/2015 02:59 PM, Gary Dale wrote:
On 25/07/15 02:52 PM, John J. Boyer wrote:
I am wondering if my Jessie system is updating its clock regularly. It
gives a
different time than my Windows box. What package contains the daemon
that updates the time from a central site?
Thanks,
John
On 07/25/2015 at 08:08 PM, Bob Bernstein wrote:
On Sun, 26 Jul 2015, Iain M Conochie wrote:
No. This is an incorrect response.
Really?
Um...your own homework, below, suggests that ntp is not the only
package that performs the task in question. Since ntpdate does not
depend on ntp,
The Wanderer writes:
The original question was What package contains the daemon that
updates the time from a central site?.
The ntp package contains such a daemon - indeed, until systemd, almost
certainly the primary such daemon.
The chrony package provides a time daemon that uses the NTP
Am 25.07.2015 um 21:26 schrieb Holger Schramm:
Am 25.07.2015 um 20:52 schrieb John J. Boyer:
I am wondering if my Jessie system is updating its clock regularly. It
gives a
different time than my Windows box. What package contains the daemon
that updates the time from a central site?
If
On Sun, 26 Jul 2015, Iain M Conochie wrote:
No. This is an incorrect response.
Really?
Um...your own homework, below, suggests that ntp is
not the only package that performs the task in
question. Since ntpdate does not depend on ntp, then I
have to say, simply REALLY!
apt-cache
Am 26.07.2015 um 02:23 schrieb The Wanderer:
The original question was What package contains the daemon that updates
the time from a central site?.
The ntp package contains such a daemon - indeed, until systemd, almost
certainly the primary such daemon. (And AFAIK the only reason it might
On Sat, 25 Jul 2015, The Wanderer wrote:
This is bordering on code-of-conduct
questionability.
I'm glad to hear that. I can see that my work here is
done.
--
I am not a loony. Why should I be tarred with the epithet
'loony' merely because I have a pet halibut? I've heard
tell that Sir
70 matches
Mail list logo
