Hello there
Would it be possible to restore some administration web UI for this
mailing list, so that I can take care of fixing cases like these, where
customer center addresses are registered as users and we get all sorts
of in the list?
Also, I wonder why it's happening. I have been
This is what I got:
[image: image.png]
Il giorno mer 27 apr 2022 alle ore 00:30 Steve 'Hollywood' Sobol - NTF <
sjso...@nwtime.org> ha scritto:
>
> On 4/26/2022 13:48, Steve 'Hollywood' Sobol - NTF wrote:
> >
> > On 4/26/2022 1:10, Opty wrote:
> >> Now that the mailing list seems to work again:
. Hence the problem.
It's a shot in the dark, but highly plausible.
Ciao
-- bronto
On Tue, 26 Apr 2022, 12:27 Marco Marongiu, wrote:
> Yep. But this time I'm left without an administrative UI, and I'm afraid
> there is little I can do without it.
>
> But I seem to understand th
Yep. But this time I'm left without an administrative UI, and I'm afraid
there is little I can do without it.
But I seem to understand that there may be something happening behind the
scenes, considering how many are complaining about missing headers. I'll
just wait for an announcement in that
Jim, can you please subscribe to the mailing list, so that I don't have to
approve manually every single post you send?
Thanks in advance
Ciao
-- bronto
Il giorno ven 25 giu 2021 alle ore 08:58 Jim Pennino
ha scritto:
> William Unruh wrote:
>
>
>
> > I suspect it is the number of times
Hi again, Opty and all
I think I found the user. They are now set to nomail. We'll see if it helps.
Ciao
-- bronto
Il giorno mar 1 giu 2021 alle ore 18:45 Marco Marongiu <
brontoli...@gmail.com> ha scritto:
> Hi Opty, all
>
> Il giorno mar 1 giu 2021 alle ore 10:26 Opt
Hi Opty, all
Il giorno mar 1 giu 2021 alle ore 10:26 Opty ha scritto:
> would e-mail headers help?
>
>
I checked those, but nothing there matches what I could get off the members
list. I *think* that it may be easier to see it from the mail server logs,
but I haven't access to those.
Let me
> changed. Can you consider it too?
>
> Thanks for the maintenance!
>
> Regards,
> Opty
>
> On Tue, May 25, 2021 at 10:20 PM Marco Marongiu
> wrote:
> > Hello again
> >
> > So FYI I have set the following two addresses to nomail:
> >
> &g
if they keep bouncing. We'll see
how they behave now.
Ciao
-- bronto
Il giorno mar 25 mag 2021 alle ore 22:13 Marco Marongiu <
brontoli...@gmail.com> ha scritto:
> Hi
>
> We have recently set most of those addresses as "nomail" in mailman: they
> are technically su
Hi
We have recently set most of those addresses as "nomail" in mailman: they
are technically subscribed to the mailing list, but they don't get any mail
-- or are not supposed to. Has that happened recently that you got an
automatic reply from those?
The only one that I don't remember to have
I think the culprit was 4359947...@email.uscc.net. I have suspended the
delivery to that address. We'll see how it goes.
Ciao
-- bronto
Il giorno lun 24 ago 2020 alle ore 09:22 Martin Burnicki <
martin.burni...@burnicki.net> ha scritto:
> Marco Marongiu wrote:
> > Me,
Me, after I replied to that email. Not sure what that means, but I wasn't
amused.
-- bronto
Il Dom 23 Ago 2020, 17:24 William Unruh ha scritto:
> On 2020-08-23, Uwe Klein wrote:
> >
> > Anybody else getting "request received" from TheFork
> > and a bunch of "undeliverable" from uscc.net
> >
Many years ago I used rrdtool to plot graphs from munin. Pretty sure there
is more modern stuff that is way better. Anyway, for what is worth:
https://syslog.me/2011/06/10/using-rrdgraph-for-better-ntp-monitoring/
I agree with David though: without knowing what information you get from
the
On 22/08/19 13:38, Charles Elliott wrote:
> FWIIW, ever since NTP.org transferred its email lists from ISC I have
> received a tiny fraction of the NTP-related email that I had in the
> past. For example, now I see two or three requests for assistance a
> month, whereas in the past there were
On 22/07/2019 11:41, Miroslav Lichvar wrote:
> Those (and yours) didn't make it back to the newsgroup where the
> question was posted. The gateway seems to work only in the direction
> to the mailing list.
Man, that newsgroup is more harmful than hail! :-D
Thanks Miroslav. That also could
On 21/07/2019 01:26, stua...@longlandclan.id.au wrote:
> after no on-list replies
Just to say that I *do* see on-list replies from "A C" and Harlan Stenn
himself, so not sure what you mean here...
-- M
___
questions mailing list
On 26/08/2018 02:51, Philip Prindeville wrote:
> Casting a wider net…
I cannot contribute with code, but it's nice to see that things are
moving. Thanks for posting it here :)
-- bronto
___
questions mailing list
questions@lists.ntp.org
On 17/01/18 00:13, Mike S wrote:
> at this point I don't see any way to get them to react other than a
> good old public shaming.
https://twitter.com/brontolinux/status/953552152626106368
Ciao!
-- bronto
___
questions mailing list
I don't know how these emails have made it through the list. Anyway, I
think I have now filtered them.
-- M
On 01/06/17 15:46, Case Solutions & Analysis wrote:
> Case Solution and Analysis of Strategy Execution Module 15: Using the Levers
> of Control to Implement Strategy by Robert L. Simons,
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
On 03/04/17 23:54, Gary E. Miller wrote:
>> I used interface ignore and then bound ntpd to specific interfaces on
>> LVS servers. This was because virtual interfaces were continuously
>> created and destroyed on those servers, ntpd had to continuosly run
>> after the change and sometimes it
On 31/03/17 22:39, Gary E. Miller wrote:
> Quick question, does anyone use either of these in ntp.conf?
>
> interface[listen | ignore | drop] [all | ipv4 | ipv6 | wildcard | name |
> address[/prefixlen]]
> nic[listen | ignore | drop] [all | ipv4 | ipv6 | wildcard | name |
> address[/prefixlen]]
Leap-second-related bug?
Il 02 Gen 2017 10:03, "Roby" ha scritto:
> Il 02/01/2017 09:43, Roby ha scritto:
>
>> Using a Risco camera that synchronizes date and time using clock.isc.org
>> NTP server via port 119
>> It works correctly for 2 years, but at the end of 2016 has
On 02/09/16 16:58, Frank Wayne wrote:
> Is there anyone that collects NTP logs with Splunk or, if not, wants
> to? (Splunk is a popular machine data indexing and analysis tool.
> They offer a free license tier.)
>
> I wrote technology add-ons (for *nix and Windows) for Splunk that do
> field
On 15/01/16 12:05, Rini van Zetten wrote:
> It seems that i have to speed up the server. It takes 5 minutes before
> its state(refid) changes from .INIT. to 127.0.0.1 (with ntpq -p on the
> client).
>
> But on the server i have no server defined, only "tos orphan 8" , so i
> cannot pass iburst.
On 15/01/16 14:20, Rini van Zetten wrote:
> I overlooked the orphanwait option. Settings this to 0 makes it work like i
> want.
Thanks for sharing your findings, may be useful to other people in the
future
Ciao
-- bronto
___
questions mailing list
On 15/01/16 13:54, Geoff Down wrote:
> Offset has been as low as .1s, currently is 1.5
0.1s is not good at all, with ntpd you should be as close as a few
milliseconds to UTC. It doesn't surprise me that ntpd doesn't enlarge
the poll interval.
Can you post the output of ntpq -p please?
What
On 14/01/16 15:26, Rini van Zetten wrote:
> The problem we have is that it takes about 5 minutes after boot
> before the devices are synchronised. Is there anything possible to
> speed up this process ?
See the burst/iburst options, that should help
Ciao
-- bronto
I've been doing a little research here.
On one server I have the munin plugins version 2.0.6 from Debian
packages in backports.
The munin plugin ntp_kernel_pll_off uses the output of ntpq -c kerninfo
or ntpdc -c kerninfo, whatever is available, then matches /^pll offset:/
and prints the value:
On 04/12/15 09:47, Marco Marongiu wrote:
> From the data we have in munin it appears that ntpd 4.2.8p3 has been
> working terribly bad during these months, to the point that when I saw
> the graphs this morning I thought that all of our servers were broken.
...unless 4.2.8p3 has ch
On 04/12/15 09:54, Marco Marongiu wrote:
> On 04/12/15 09:47, Marco Marongiu wrote:
>> From the data we have in munin it appears that ntpd 4.2.8p3 has been
>> working terribly bad during these months, to the point that when I saw
>> the graphs this morning I thought that al
Hi there
Due to challenges to produce our own Debian packages for 4.2.8p4 to fix
DSA-3388[1], we decided to downgrade to the 4.2.6 packages in bundle
with Debian 6, 7 and 8. We had been running 4.2.8p3 since late June to
implement our own countermeasures for the leap second[2].
>From the data we
On 24/11/15 10:44, Miroslav Lichvar wrote:
>> > What option would you recommend?
> I think the recommendation is to not use the limited option at all.
> Some people reported that it may actually increase the amount of
> traffic, apparently there are broken clients that send a new request
> soon
Hi all
In the document "ntpd access restrictions" it is recommended to use the
restriction "kod"[1]. However, when used as it is there it makes ntpd
complain:
> Nov 20 11:54:00 testnode ntpd[40098]: restrict ::: KOD does nothing without
> LIMITED.
The documentation agrees[2].
Now I have two
On 12/11/15 06:49, Tiwari, Dilip (Nokia - IN/Bangalore) wrote:
> As per my understanding if true option is used with it, it'll escape/survive
> select and cluster algorithm, and will always be selected as preferred server.
> I used server command this way: server -4 true iburst minpoll 4
>
Hi there
Following this: https://www.debian.org/security/2015/dsa-3388
I would kindly ask if the fixes for 4.2.8p4 have already landed the
official source code and, if not, when will they?
Thanks, ciao!
-- bronto
___
questions mailing list
I can't really say, posting your full ntp.conf could help better.
Are you syncing against public or internal ntp servers?
Regards
-- M
On 18 Sep 2015 17:14, "sneha b" wrote:
> Hi,
>
> NTP is not syncing immediately, its taking some 3 minutes time.
> I want to sync
Hi there
Did the output of any command change between a.2.6 and 4.2.8? The moment
we have upgraded ntpd to 4.2.8p3-RC1 our munin graphs for time offset
went crazy but the servers are behaving. The only thing I can think of
is that some command changed output and the plugins are unable to decode
Hi there!
Will it be out soon enough before June 30th?
Ciao
-- bronto
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
On 23/06/15 10:03, Harlan Stenn wrote:
Will it be out soon enough before June 30th?
I'm hoping for the 25th.
Understood
We're going thru some last-minute discussions and implementation/testing
of some leap-smear ideas. I would not be surprised to discover that we
will need a p4 to handle
On 12/06/15 10:07, Joachim Fabini wrote:
I want ntp to listen exclusively to the local GPS/PPS
signal (server 127.127.20.0) and ignore all other network interfaces,
messages, events
Use the interface directive, e.g.:
interface ignore all
interface listen 127.127.20.0
Ciao
-- bronto
On 12/06/15 11:54, Joachim Fabini wrote:
The straight-forward solution that you propose was the one that I tried
first. Unfortunately it does not work.
Then I guess I don't understand what you're after exactly. I'll re-read
your message entirely and check what I misunderstood. Sorry for the
On 10/06/15 13:02, Kashif Mumtaz Tahir wrote:
is there anything we need to change /modify
It depends on what you want to achieve. I am upgrading to 4.2.8p3 and
setting tinker step 0 and disable kernel in the configuration
because I am trying to avoid clock stepping at all cost. What about you?
Hi there
Miroslav Lichvar, whom you have read several times in this list, has put
together a very nice set of five possible ways to handle the leap second
with both ntpd and chrony.
http://developerblog.redhat.com/2015/06/01/five-different-ways-handle-leap-seconds-ntp/
As you may have noticed
On 26/05/15 20:29, Harlan Stenn wrote:
I'm expecting to release p3 this week, leaving room for a p4 if needed
before June 30th.
If folks would rather see only a p3, I can hold off on that release
until the 15th of June or so.
I think you know better than anyone else what's the best thing to
Hi Harlan
On 23/05/15 21:11, Harlan Stenn wrote:
Please see if putting:
rlimit memlock 0
into your ntp.conf file will fix this.
Yes, that fixed it and now ntpd is behaving exactly as I expected.
Thanks for the support.
Besides, I found that jessie was also acting up so I defaulted to
Hi Harlan, all
On 21/05/15 20:48, Harlan Stenn wrote:
The way to fix that is for you to specify --enable-local-libopts on your
'configure' line.
I managed to compile them on all the three versions. The configure
command lines are below.
Anyway, I am getting some weird problems in squeeze.
On 21/05/15 20:48, Harlan Stenn wrote:
Hi Marco,
Glad to see questions@ is working!
:-D
The problem you are seeing is that you seem to have libopts installed on
your system, and the version installed there is an older version than
the one we need.
The way to fix that is for you to
Hi there
Is it a known problem that ntpd 4.2.8p3-RC1 doesn't compile on Debian
Linux 6 (squeeze) and 7 (wheezy)? If it's supposed to work, what am I
doing wrong? (See errors below)
In scope of my leap second experiments it's quite interesting that this
bug was fixed:
* [Bug 2745] ntpd -x steps
Hi all
Last Friday I found something, potentially a very bad bug, in Linux when
a leap second is handled.
http://syslog.me/2015/05/16/scary-times-at-the-leap-second-lab/
I am not sure where the problem stems from and as of now I'm leaning on
something in the system rather than in ntpd. However,
On 13/05/15 13:23, Miroslav Lichvar wrote:
I'm not sure what exactly are you asking here. Do you see in your
testing or the source code something different from what is described
in the document?
No, I am trying to understand if what I understand* from the
documentation is correct.
* sorry
On 13/05/15 11:03, Miroslav Lichvar wrote:
On Tue, May 12, 2015 at 11:33:31AM +0200, Marco Marongiu wrote:
On 12/05/15 11:28, Marco Marongiu wrote:
Hi there
In http://doc.ntp.org/4.2.6p5/ntpd.html#leap I read: If the leap is in
the future less than 28 days, the leap warning bits are set
Hi there
In http://doc.ntp.org/4.2.6p5/ntpd.html#leap I read: If the leap is in
the future less than 28 days, the leap warning bits are set.
What are the practical consequences of the warning bits being set? Will
they cause the leap second to be armed in the kernel eventually? What if
the kernel
On 12/05/15 11:28, Marco Marongiu wrote:
Hi there
In http://doc.ntp.org/4.2.6p5/ntpd.html#leap I read: If the leap is in
the future less than 28 days, the leap warning bits are set.
What are the practical consequences of the warning bits being set? Will
they cause the leap second
23:59:59 of which timezone?
Il 02/apr/2015 03:14 Jim Witschey jim.witsc...@datastax.com ha scritto:
Hey all,
I'm trying to simulate a leap second on a cluster of Ubuntu AWS
instances via NTP, and I could use some help. I've set up a basic NTP
server with a leapfile as described here:
On 12/03/15 00:09, Harlan Stenn wrote:
Charles Babcock wrote an article about NTP and me and NTF and ...
http://www.informationweek.com/it-life/ntps-fate-hinges-on-father-time/d/d-id/1319432?
Argh...
___
questions mailing list
On 09/02/15 11:49, Miroslav Lichvar wrote:
I was wondering what others think about handling leap seconds when
ntpd is running in the slew only mode (-x option).
[...]
In 4.2.6 was added support for leap seconds in the daemon loop and
ntpd now steps the clock by calling settimeofday() or
Hi Harlan, and thanks. Comments below
On 06/02/15 23:44, Harlan Stenn wrote:
Debian Squeeze doesn't have a patched package available in the
squeeze-lts series yet. On those clients would a restriction like
restrict ::1 ignore
mitigate the vulnerability?
I think so, but it will also
Hi David, and thanks for answering
On 06/02/15 14:44, David Woolley wrote:
Debian Squeeze doesn't have a patched package available in the
squeeze-lts series yet. On those clients would a restriction like
restrict ::1 ignore
mitigate the vulnerability?
Sounds more like you need to fix
Hi there
I'm referring to this one in particular: ::1 can be spoofed on some
OSes, so ACLs based on IPv6 ::1 addresses can be bypassed.
Debian Squeeze doesn't have a patched package available in the
squeeze-lts series yet. On those clients would a restriction like
restrict ::1 ignore
mitigate
On 21/01/15 15:31, Mike S wrote:
On 1/21/2015 2:10 AM, Mike Cook wrote:
And one of the reasons why a significant portion of the computing
community wants to get rid of leap seconds. A coverup for bad
engineering practices.
That's right. Instead of recognizing that the world rotates on it's
On 19/01/15 09:25, Martin Burnicki wrote:
Marco Marongiu wrote:
On Linux it worked correctly... That is?
Yes. My first tests were more focused on Windows in different versions,
and I used just another Linux box with a simple setup (just NTP client,
no leap second file) to compare
On 19/01/15 14:47, Martin Burnicki wrote:
Actually I've tested a 4.2.8 client on Linux which only receives the
leap second warning from an upstream NTP server.
There are other configuration options like presence of a leapsecond
file, NTP server mode receiving the announcement from a
On 15/01/15 03:06, Harlan Stenn wrote:
I'm trying to figure out if anybody is actively using autokey, in a
production deployment.
If you are, please let me know - I have some questions for you.
That's in my TO-DO list since at least 2011. When I tried to configure
it at the time and on the
On 12/01/15 06:10, William Unruh wrote:
I also admit I do not know how windows impliments leap
seconds.
I don't have a reference, but I remember that at the time of the latest
leap second I read that Windows will half the clock speed at 23:59:59 so
that it reaches 00:00:00 at the right time.
On 12/01/15 11:48, Martin Burnicki wrote:
Fortunately Dave Hart had some time to have a closer look at this, and
fix it for 4.2.6, so unless something has been broken again in the mean
time it should be fixed in 4.2.6 and later, and should work correctly.
Let me understand: you mean that in
Get ready, fellows. It's coming again.
-- bronto
Forwarded Message
Subject: Bulletin C number 49
Date: Mon, 05 Jan 2015 14:25:49 +0100
From: IERS EOP Product Center services.i...@obspm.fr
Reply-To: IERS EOP Product Center services.i...@obspm.fr
To: bulc.i...@obspm.fr
On 12/18/2014 01:08 PM, saxenaakas...@gmail.com wrote:
I have configured NTP version 4.2.6 server on fedora 20 machine.
server side I am using local system time and given a broadcast subnet
and all other options are disabled and on client's side I enabled
only broadcast client. I haven't given
On 08/12/14 04:00, Harlan Stenn wrote:
Several more volunteers (coders and sysadmin typs) would be great,
too.
Can you please elaborate on what kind of help do you need from sysadmin
folks, please?
Ciao!
-- bronto
___
questions mailing list
On 11/11/2014 10:17 AM, Harlan Stenn wrote:
Does anybody have a good reason why we should keep these around for the
'restrict' case?
No good reason to keep that, but I'd still support them by making those
options no-ops and throwing a warnings both on console and syslog.
-- M
Apologies for this question not being 100% pertinent to ntpd, but I'd
need an authoritative answer and there is no place like this list to
find real expert of computer clocks and time synchronization.
Too many wannabes and professed experts out there.
Plenty here too?
Possibly. But the
Hi all
Apologies for this question not being 100% pertinent to ntpd, but I'd
need an authoritative answer and there is no place like this list to
find real expert of computer clocks and time synchronization. Too many
wannabes and professed experts out there.
I have some empirical experience
On 09/15/2014 09:54 AM, Brian Inglis wrote:
You could also set up your routers as stratum 3 peering with other
nearby routers and using some nearby Linux hosts as stratum 2 servers.
call me picky, but I strongly prefer that routers mind their own
business, at which they are supposed to be good,
I understand that clients in one DC will use both the NTP servers in the
same DC and in the other one. Is my understanding correct?
On 09/04/2014 10:03 AM, Mike Edwards wrote:
The DCs support remote offices. I am thinking of configuring the
Linux hosts with 3 time servers, the two at the
On 09/03/2014 08:51 AM, David Woolley wrote:
On 01/09/14 17:01, gooly wrote:
I just installed ntp on my Win 7 pc where it runs perfectly the
difference is around 0,5 sec.
500ms is very bad.
Then I installed ntp on my 2008 R 2vps where the delay gets bigger and
bigger, around 12 sec per
Il 02/20/2014 06:21 AM, Harlan Stenn ha scritto:
Folks,
Just in case you might be interested, I published a blog post about NTP
and the recent attacks:
http://nwtime.org/ntp-winter-2013-network-drdos-attacks/
The site is not reachable at the moment. Maybe it's under attack? :)
-- bronto
On 01/26/2014 08:08 PM, Rob wrote:
My hypothesis is that the ARP entry for the NTP server has timed out,
and when ARP has to resolve an entry in some implementations the first
packet is always lost (it is not cached pending a reply).
When the cycle is 1024 seconds, the ARP entry has again
Il 01/24/2014 12:09 AM, David Woolley ha scritto:
3) second filter: a new value for the error that fits the majority of
these C references is calculated; the L references that don't fit in
this error interval are called outlyers; the S=C-L references that
remain are considered;
Ones that
Il 01/23/2014 09:42 PM, Brian Inglis ha scritto:
According to book Expert Network Time Protocol from PETER RYBACZYK:
I don't have that book. I'd appreciate that anyone in this list that has
reviewed the book can give their opinion about it.
Hi Peter
In your questions, you are showing configuration snippets as they were
taken from some authoritative source. Would you mind sharing that source?
As for me, I consider the following to be *the* authoritative sources
for anything NTP:
http://www.eecis.udel.edu/~mills/ntp/html/index.html
On 01/23/2014 11:00 AM, ardi wrote:
On Thursday, January 23, 2014 9:36:35 AM UTC+1, Marco Marongiu wrote: Well,
I have come across almost all of the pages, you are mentioning below,
but it seems, i have combined the info wrongly for my example...:-)
:-)
Does it mean these minpoll, maxpoll
On 01/23/2014 12:52 PM, ardi wrote:
Reading: http://www.ntp.org/ntpfaq/NTP-s-algo-real.htm#Q-NTP-ALGO
Two time sources cannot be split into two parties where one has a majority.
What does this majority means?
It's in the sentence: all values must lie within the error interval the
majority of
On 01/23/2014 04:16 PM, Brian Utterback wrote:
On 1/23/2014 8:06 AM, Marco Marongiu wrote:
If you have just two references, the step 2) doesn't bring you anywhere
as it is impossible to reach a majority. It's like you're skipping step
2), and the results lose accuracy.
Not to put too fine
Il 12/27/2013 04:27 AM, Williams Catherine ha scritto:
I want to simulate leap second case. I have one linux server as NTP server.
How can I make the server get leap second indicate?
I did leap second simulations before the latest one, and wrote a blog
post with some detail. Check this:
Hi all
A colleague contacted me yesterday and asked:
You being somewhat tied to the NTP world, hear anything about public
NTP servers being used for amplification in ddos attack?
I haven't heard anything about that. Have you? In case, anything you can
share about that?
Thanks, ciao!
--
I looked up dns, resol, and ip to no avail.
Am I missing something?
Maybe dynamic or pool?
http://archive.ntp.org/ntp4/ChangeLog-dev
Thanks!
-- M
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
Il 08/05/2013 07:40 PM, Steve Kostecke ha scritto:
The ChangeLog for production releases may be viewed on-line at
http://archive.ntp.org/ntp4/ChangeLog-stable
The documentation for production releases is archived at
http://doc.ntp.org
Thanks Steve, I knew the doc website, but not the
Hi all
I think I remember that older versions of ntpd did name resolution only
upon start, while more recent ones check the name/IP association every
once in a while.
Assuming I remember well, in which version was this change introduced?
Are there configuration options that control this
On 24/05/2013 07:42, Riccardo Castellani wrote:
What do you think for my architecture about this configuration in my ntp.conf
for all 3 servers:
I never use them
Ciao!
-- bronto
___
questions mailing list
questions@lists.ntp.org
On 21/05/2013 14:31, Riccardo Castellani wrote:
n.4 srv Internet-- server A
server A -- server B
server
A -- server C
A is my internal source
B,C are cluster machine so hardware
is reliable but I don't want to present these servers directly on pubblic
network
My comments:
1)
Il 03/27/2013 10:24 PM, unruh ha scritto:
You do NOT want to hard code anything into your program. That is
extremely bad form, unless that address is one controlled by you.
Indeed. Robert, please see:
http://en.wikipedia.org/wiki/NTP_server_misuse_and_abuse
and in particular:
On 09/01/13 20:21, dar8...@eml.cc wrote:
i'm not sure if/how to implement this conditional fallback 'logic' for
ntp's server selection.
I had a similar problem, and I use cfengine to solve that: depending on
the network to which I am attached, my ntpd gets a different
configuration: Italian
On 01/08/12 04:40, jclerm...@gmail.com wrote:
Yes, this affected us. Can someone explain why this was done? Was
it designed to be a test of some kind? The Linux leap second kernel
bug that was discovered a month ago was only patched on July 17; that
patched kernel has presumably not made it
On 01/08/12 10:28, Marco Marongiu wrote:
I tried to collect some information around the globe, but with scarce/no
feedback. I am *suspecting* that this could be a rather imaginative
attempt to DOS worldwide.
Anyway, a colleague of mine is now hunting down some upstreams that
faked the leap
On 01/08/12 14:58, Marco Marongiu wrote:
Question now is: assuming those servers were running ntpd, was such a
bug reported at some point?
Plus, another question. If one uses the leapfile, are spurious leap
second notifications like this one discarded?
From the docs at http://doc.ntp.org/4.2.6
Hi all
This is just to warn you that there are now some NTP servers around the
globe spreading a leap second announcement for tomorrow 00:00:00 UTC
(so, basically, in a few hours now).
If you didn't take action before the leapocalypse last month, you better
hurry now.
Ciao
-- bronto
Hi all
I assume everyone has read the reports about the mess connected to the
announcement of a leap second and bugs in Linux and Java. Anyway,
reports suggest that the calls of adjtimex by ntpd, related to the leap
second announcement, made the Linux kernel hang in heavy load conditions.
My
...on June 30th/July 1st transition, so we'll have:
June 30th 23:59:59
June 30th 23:59:60
July 1st 00:00:00
The question is: does it happen at 00:00:00 UTC (so it must be shifted
ahead/behind depending on the timezone) or, by convention, it happens at
00:00:00 at the local timezone?
I am quite
On 25/05/2012 15:01, Miguel Gonçalves wrote:
It happens at 23:59:59 UTC:
ftp://hpiers.obspm.fr/iers/bul/bulc/bulletinc.dat
The bulletin states that the leap second is introduced at the end of
June so 00:00:00 is not a possibility because it is already July.
thanks a lot Miguel!
Ciao
--
Hi Martin, all
On 12/03/12 12:16, Martin Burnicki wrote:
In my post from the earlier thread I wrote:
Then you should set UTC time on that server close to (maybe 1 or 2 hours
before) midnight for the correct leap second date, e.g. 22:00 UTC on
June 30, 2012, and start ntpd on the server.
1 - 100 of 128 matches
Mail list logo