Dennis Wicks writes:
> Mart van de Wege wrote on 07/27/2015 12:49 AM:
>> Gary Dale writes:
>>
>>> On 26/07/15 02:44 PM, Mart van de Wege wrote:
Gary Dale writes:
>>> Upgrading to sid is asking for trouble. Sid isn't called unstable for
>>> nothing.
>>
>> I know. I really do. I only ha
Mart van de Wege wrote on 07/27/2015 12:49 AM:
Gary Dale writes:
On 26/07/15 02:44 PM, Mart van de Wege wrote:
Gary Dale 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
Renaud (Ron) OLGIATI wrote on 07/26/2015 03:40 PM:
On Sun, 26 Jul 2015 15:27:50 -0500
John Hasler 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 G
Gary Dale writes:
> On 26/07/15 02:44 PM, Mart van de Wege wrote:
>> Gary Dale 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, someone's gotta run Sid, or it'll ne
On 26/07/15 02:44 PM, Mart van de Wege wrote:
Gary Dale 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 th
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 a
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.
N
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 daem
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 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 ver
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
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 provi
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
On Sun, 26 Jul 2015 15:27:50 -0500
John Hasler 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,
Ron.
--
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 debian-user-requ...@lists.debia
hat the authentication system is Autokey, but see above.
> > Even without it, though, sucessfully spoofing all four of the servers
> > you use would be challenging.
>
> > I don't see why this would be difficult for someone who controls the
> > local network (e.g. the wifi
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,
Gary Dale 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 upgrading. :)
I actu
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
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 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 adequa
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 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 tel
Sven Hartge 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 debian-user-requ.
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 nt
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 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
n without it, though, sucessfully spoofing all four of the servers
> you use would be challenging.
> I don't see why this would be difficult for someone who controls the
> local network (e.g. the wifi hotspot).
If your laptop needs precise time and you are a target for such attacks
tak
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 wo
> 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
jha
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 USA
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 th
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-tim
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 ac
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 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 inst
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
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
> > s
On Sun 26 Jul 2015 at 14:57:02 +0200, Sven Hartge wrote:
> Michael Biebl wrote:
>
> > The assumption here is, that if the admin explicitly installed ntp, it
> > should be preferred of systemd-timesyncd.
> > See
>
> > /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
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 se
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
> >>
> >>
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 system is updating its c
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
On Sunday 26 July 2015 13:17:02 Renaud OLGIATI wrote:
> On Sun, 26 Jul 2015 10:54:35 +0100
>
> Lisi Reisz 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
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
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
give
On Sun, 26 Jul 2015 10:54:35 +0100
Lisi Reisz 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 systemd has, as a stroke
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 listm
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 d
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 v
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
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 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
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 d
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 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 de
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 tim
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 Ge
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 mi
ystemd's "we're already here, so
you might as well use our tools instead of looking for alternatives"
effect, analogously to how IE got its dominant market share.)
In the "systemd era", just listing ntp is indeed incomplete, and I
wouldn't have been comfortable giv
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 search
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
On Sat, 25 Jul 2015 19:08:33 -0400 (EDT)
Bob Bernstein 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.
--
La perfec
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 settin
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 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?
>>
>> Than
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. Se
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 diff
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 debian-user-r
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, Wi
Ralph Winslow writes:
> I've forgotten the name of the package that provides a daemon to
> synchronize the time on my workstation to specified time-servers
> on the net. Could some kind soul jog my memory?
xntp3 is in 2.0 and frozen, and there is chrony in unstable. chrony is,
IMHO, much easier
I don't think it runs in daemon mode but I always use netdate - I have
mine in a script for ip.up so it synchs every time I connect and also
runs 'hwclock --systohc --utc'.
HTH, G.S.
---Ralph Winslow <[EMAIL PROTECTED]> wrote:
>
> I've forgotten the name of the package that provides a daemon to
>
On 6 Jan, Ralph Winslow wrote:
> I've forgotten the name of the package that provides a daemon to
> synchronize the time on my workstation to specified time-servers
> on the net. Could some kind soul jog my memory? TIA
>
> --
> -
> Ralph Winslow
I've forgotten the name of the package that provides a daemon to
synchronize the time on my workstation to specified time-servers
on the net. Could some kind soul jog my memory? TIA
--
-
Ralph Winslow [EMAIL PROTECTED]
The IQ of the group
74 matches
Mail list logo
