gaurav10ni...@gmail.com wrote:
> On Wednesday, 10 May 2017 21:27:27 UTC+5:30, David Taylor wrote:
> I want to get offset between 0.5-2 ms. Can it be achieved using meinberg
> application?
Please note "the meinberg application" is just a set of precompiled
binaries built from the original NTP
On 26/05/2017 12:59, gaurav10ni...@gmail.com wrote:
[]> Hi David,
I want to get offset between 0.5-2 ms. Can it be achieved using meinberg
application?
If yes, Kindly share the parameters required to be changed to get offset value
in the required range.
Regards,
Gaurav
Gaurav,
As with
On Wednesday, 10 May 2017 21:27:27 UTC+5:30, David Taylor wrote:
> On 10/05/2017 14:40, gaurav10ni...@gmail.com wrote:
> []
> > Hi Jacob,
> >
> > Can you please share the procedure for implementing version 4 of NTP client
> > on windows 7?
> >
> > Regards,
> > Gaurav
>
> Gaurav,
>
> Meinberg
On 12/05/2017 06:33, Jakob Bohm wrote:
[]
Note that all recent/current versions of the Windows Time Service are
in fact SNTP/NTP implementations, with quality of implementation
improving in newer versions.
Old (now unsupported) versions of the Windows Time Service violated the
SNTP/NTP
On 10/05/2017 15:03, David Taylor wrote:
On 10/05/2017 07:03, Jakob Bohm wrote:
[]
Using NTP 4.2.8p10 instead of the Windows Time Service doesn't make
sense on most Windows machines, but it does make sense in some
situations where the Windows Time Service included with Windows cannot
be
On Wednesday, 22 March 2017 18:57:36 UTC+5:30, David Taylor wrote:
> NTP 4.2.8p10 released
>
> Windows binaries working on Windows-XP SP3 & later - download:
> http://www.satsignal.eu/ntp/x86/index.html
>
> Source: http://archive.ntp.org/ntp4/ntp-4.2/ntp-4.2.8p10.tar.gz
>
> --
> Cheers,
>
On 2017-05-09 01:45, ashu6...@gmail.com wrote:
> How can we add redundant server into NTP 4.2.8p10 ? If we try to
> edit the configuration file it's not switching to the redundant
> server?
After changing the /etc/ntp.conf file, you need to restart any
server ntp daemon using it to put changes
ashu6...@gmail.com wrote:
> Hi david,
> How can we add redundant server into NTP 4.2.8p10 ? If we try to
> edit the configuration file it's not switching to the redundant
> server?
The NTP reference implementation (ntpd) does not use redundancy in the
way you might expect. I.e., you can't
On 09/05/17 09:45, ashu6...@gmail.com wrote:
> How can we add redundant server into NTP 4.2.8p10 ? If we try to
> edit the configuration file it's not switching to the redundant
> server?
Maybe it's just me or I am dumb, but I am not sure I understand what you
are talking about. Could you
Hi david,
How can we add redundant server into NTP 4.2.8p10 ? If we try to edit the
configuration file it's not switching to the redundant server?
Regards
Ashish
On Thursday, 23 March 2017 21:40:04 UTC+5:30, Martin Burnicki wrote:
> David Taylor wrote:
> > NTP 4.2.8p10 released
> >
> >
On 07/04/2017 08:33, seema pandhre wrote:
On Wednesday, March 22, 2017 at 6:57:36 PM UTC+5:30, David Taylor wrote:
NTP 4.2.8p10 released
Windows binaries working on Windows-XP SP3 & later - download:
http://www.satsignal.eu/ntp/x86/index.html
Source:
On Wednesday, March 22, 2017 at 6:57:36 PM UTC+5:30, David Taylor wrote:
> NTP 4.2.8p10 released
>
> Windows binaries working on Windows-XP SP3 & later - download:
> http://www.satsignal.eu/ntp/x86/index.html
>
> Source: http://archive.ntp.org/ntp4/ntp-4.2/ntp-4.2.8p10.tar.gz
>
> --
> Cheers,
On 27/03/2017 22:34, Dan Gearty wrote:
Hi David, that is interesting that the problem does not manifest across the
board given Martin's description of the bug.
I am using the Meinberg build on Windows 10 Pro.
I had previously been depending upon the environment variable.
Dan,
Dan Gearty wrote:
> I have been using the loopback driver on Windows 10. It had been
> running OK in older versions up to 4.2.8p9. Now in 4.2.8p10 it
> appears that junk characters are appended to the driver name when it
> is called. The junk characters are different each time NTP is
>
On 25/03/2017 22:09, Dan Gearty wrote:
I have been using the loopback driver on Windows 10.
It had been running OK in older versions up to 4.2.8p9.
Now in 4.2.8p10 it appears that junk characters are appended to the driver
name when it is called. The junk characters are different each time NTP
On 2017-03-25 22:57, Brian Inglis wrote:
> On 2017-03-25 16:09, Dan Gearty wrote:
>> I have been using the loopback driver on Windows 10.
>> It had been running OK in older versions up to 4.2.8p9.
>> Now in 4.2.8p10 it appears that junk characters are appended to the
>> driver name when it is
On 2017-03-25 16:09, Dan Gearty wrote:
> I have been using the loopback driver on Windows 10.
> It had been running OK in older versions up to 4.2.8p9.
> Now in 4.2.8p10 it appears that junk characters are appended to the
> driver name when it is called. The junk characters are different each
>
I have been using the loopback driver on Windows 10.
It had been running OK in older versions up to 4.2.8p9.
Now in 4.2.8p10 it appears that junk characters are appended to the driver
name when it is called. The junk characters are different each time NTP is
restarted.
25 Mar 16:57:32
Hi,
I asked my original question to see if the process could be improved.
For instance, it would be good if there was direct pointers to the
various distributions page where packaging state and availability for
various releases would be shown and updates. This is what can be found
for
Hal,
Thanks - we're going over the lists and processes to improve things.
H
--
Hal Murray writes:
>
> Harlan said:
> > We're open to doing an even better job of telling folks about things like
> > this.
>
> I think a message should go out to (almost?) all lists when security fixes
> are
Harlan said:
> We're open to doing an even better job of telling folks about things like
> this.
I think a message should go out to (almost?) all lists when security fixes
are available to the general public.
The first mail on questions was David Taylor's announcement of the
availability of
Martin Burnicki writes:
> Dan Geist wrote:
> > I don't disagree, but along with membership in the consortium comes
> > additional benefits like that.
> >
> > I'm guessing Suse, FreeBSD, and Debian were all had the opportunity
> > to be working on patched versions a couple weeks ago when the NTF
>
Dan Geist wrote:
> I don't disagree, but along with membership in the consortium comes
> additional benefits like that.
>
> I'm guessing Suse, FreeBSD, and Debian were all had the opportunity
> to be working on patched versions a couple weeks ago when the NTF
> folks sent out the original
Magnus Danielson wrote:
> Hi,
>
> On 03/23/2017 05:12 PM, Martin Burnicki wrote:
>> Magnus Danielson schrieb:
>>> Hi Martin,
>>>
>>> On 03/23/2017 03:25 PM, Martin Burnicki wrote:
Hi Magnus,
Magnus Danielson wrote:
> Hi,
>
> On 03/22/2017 02:27 PM, David Taylor wrote:
Magnus Danielson writes:
> Hi,
>
> On 03/23/2017 05:12 PM, Martin Burnicki wrote:
> > Magnus Danielson schrieb:
> >> Hi Martin,
> >>
> >> On 03/23/2017 03:25 PM, Martin Burnicki wrote:
> >>> Hi Magnus,
> >>>
> >>> Magnus Danielson wrote:
> Hi,
>
> On 03/22/2017 02:27 PM, David
Hi,
On 03/23/2017 05:12 PM, Martin Burnicki wrote:
Magnus Danielson schrieb:
Hi Martin,
On 03/23/2017 03:25 PM, Martin Burnicki wrote:
Hi Magnus,
Magnus Danielson wrote:
Hi,
On 03/22/2017 02:27 PM, David Taylor wrote:
NTP 4.2.8p10 released
Windows binaries working on Windows-XP SP3 &
Magnus Danielson schrieb:
> Hi Martin,
>
> On 03/23/2017 03:25 PM, Martin Burnicki wrote:
>> Hi Magnus,
>>
>> Magnus Danielson wrote:
>>> Hi,
>>>
>>> On 03/22/2017 02:27 PM, David Taylor wrote:
NTP 4.2.8p10 released
Windows binaries working on Windows-XP SP3 & later - download:
David Taylor wrote:
> NTP 4.2.8p10 released
>
> Windows binaries working on Windows-XP SP3 & later - download:
> http://www.satsignal.eu/ntp/x86/index.html
>
> Source: http://archive.ntp.org/ntp4/ntp-4.2/ntp-4.2.8p10.tar.gz
And a full-featured installer including the current openSSL DLL is now
Hi Martin,
On 03/23/2017 03:25 PM, Martin Burnicki wrote:
Hi Magnus,
Magnus Danielson wrote:
Hi,
On 03/22/2017 02:27 PM, David Taylor wrote:
NTP 4.2.8p10 released
Windows binaries working on Windows-XP SP3 & later - download:
http://www.satsignal.eu/ntp/x86/index.html
Source:
Hi Magnus,
Magnus Danielson wrote:
> Hi,
>
> On 03/22/2017 02:27 PM, David Taylor wrote:
>> NTP 4.2.8p10 released
>>
>> Windows binaries working on Windows-XP SP3 & later - download:
>> http://www.satsignal.eu/ntp/x86/index.html
>>
>> Source:
Hi,
On 03/22/2017 02:27 PM, David Taylor wrote:
NTP 4.2.8p10 released
Windows binaries working on Windows-XP SP3 & later - download:
http://www.satsignal.eu/ntp/x86/index.html
Source: http://archive.ntp.org/ntp4/ntp-4.2/ntp-4.2.8p10.tar.gz
Is bugs generated in distros?
Debian for instance.
NTP 4.2.8p10 released
Windows binaries working on Windows-XP SP3 & later - download:
http://www.satsignal.eu/ntp/x86/index.html
Source: http://archive.ntp.org/ntp4/ntp-4.2/ntp-4.2.8p10.tar.gz
--
Cheers,
David
Web: http://www.satsignal.eu
___
32 matches
Mail list logo
