matthew.sel...@twosigma.com said:
> "rlimit memlock 0" using Classic causes ntpd to died after 3 minutes with
> this error 2016-06-29T00:13:21.903+00:00 host.example.com ntpd[27206]:
> libgcc_s.so.1 must be installed for pthread_cancel to work
What version of Classic are you running? I though t
On Tue, Jun 28, 2016 at 07:26:39PM -0400, Eric S. Raymond wrote:
> Hal Murray :
> > I think you have extrapolated from some modern systems to our whole target
> > environment. I don't remember any discussion supporting memlock not being
> > interesting/important.
>
> There were actually two thr
In recent discussion of the removal of memlock, Hal Murray said
"Consider ntpd running on an old system that is mostly lightly loaded
and doesn't have a lot of memory."
By doing this, he caused me to realize that I have not been explicit
about some of the assumptions behind my technical strategy.
Yo Eric!
On Tue, 28 Jun 2016 19:47:14 -0400
"Eric S. Raymond" wrote:
> Gary E. Miller :
> > Yo Eric!
> >
> > On Tue, 28 Jun 2016 19:26:39 -0400
> > "Eric S. Raymond" wrote:
> >
> > > (You should camp on #ntpsec. Also join our Signal channel -
> > > because that's secured, most of the vuln
Gary E. Miller :
> Yo Eric!
>
> On Tue, 28 Jun 2016 19:26:39 -0400
> "Eric S. Raymond" wrote:
>
> > (You should camp on #ntpsec. Also join our Signal channel - because
> > that's secured, most of the vuln discussions happen there.)
>
> Ah, how do we joing the Signal channel?
Install Signal on
Yo Eric!
On Tue, 28 Jun 2016 19:26:39 -0400
"Eric S. Raymond" wrote:
> (You should camp on #ntpsec. Also join our Signal channel - because
> that's secured, most of the vuln discussions happen there.)
Ah, how do we joing the Signal channel?
RGDS
GARY
--
Hal Murray :
> There may have been a general idea that flag4 would be used to
> enable clockstats from an individual driver instance.
I'm getting that impression, yes.
By the way, the one change I made immediately after putting that table
together was to add a 'subtype' option keyword that is an
Hal Murray :
> I think you have extrapolated from some modern systems to our whole target
> environment. I don't remember any discussion supporting memlock not being
> interesting/important.
There were actually two threads about this attached to memlock-related bug
reports in Classic. They ini
e...@thyrsus.com said:
> One thing that jumps out at me is that several drivers have a clockstats
> verbosity option, always flag4 (which, alas, is used for other things too).
There may have been a general idea that flag4 would be used to enable
clockstats from an individual driver instance.
T
e...@thyrsus.com said:
> After discussion with Daniel about the performance and security issues I
> deleted the memlock code. As the comment explains:
I think changes like that are worthy of a general announcement.
> on modern systems, which swap so seldom
> that many people don't bother wit
Hal Murray :
> bps may not be enough. There is also the parity and stop bits, but I don't
> think they are fiddled much.
>
> The HP driver uses one mode bit to switch from whatever the default is to a
> different baud rate and parity. It may be simpler to use a device-type
> keyword rather th
I have a pool server. mru maxmem is set big enough to capture a whole day.
Each midnight, a cron job fires off to capture everything to a file. The
file is 100 megabytes.
While that is going on, ntpq is using 95% of the cpu.
If anybody is looking for a nice distraction, it would be interesti
12 matches
Mail list logo
