> Ah, it's probably doing a sigsuspend(2).
I doubt it. That ties up your process/thread waiting for a signal. If you
want to wait for IO, there are simpler ways.
My guess was sigprocmask(2). They way that I discovered that somebody was
masking SIGINT was using it to read the current mask.
Hal Murray :
>
> e...@thyrsus.com said:
> > I don't know of any functions that are specifically unsafe around setjmp()/
> > longjmp().
>
> The interesting case is longjmp-ing from a signal handler.
Right. I believe the way a signal handler works is actually like a
setjmp/longjmp; that is, on re
On Wed, Jan 27, 2016 at 2:45 AM, Mark Atwood
wrote:
> My lesson I take away from that is not that I am some special fount of
> valuable ideas, but that nearly everyone who works in the right parts of
> the tech space is, but that means little, as ideas are cheap, it's
> execution that is valuable
On Wed, Jan 27, 2016 at 5:06 AM, Amar Takhar wrote:
> This also means we can remove the 'waf' binary from the Git repository and
> package it in with the tarball releases in the future
>
Speaking for ease of use for me, I would prefer not to think about which
waf version to use when building fro
e...@thyrsus.com said:
> I don't know of any functions that are specifically unsafe around setjmp()/
> longjmp().
The interesting case is longjmp-ing from a signal handler.
> The right way to think about setjmp()/longjmp() is as a save/restore of the
> processor's register state, including the
Hal Murray :
> I'm fishing for a list of routines that shouldn't be used with longjmp
> similar to the list that shouldn't be used with threads, or rather for the
> discussion of that list.
I don't know of any functions that are specifically unsafe around
setjmp()/longjmp().
The right way to th
Hal Murray :
> I haven't figured out if this is a bug in getnameinfo or if longjmp-ing is
> basically evil.
I wouldn't say "evil" exactly, but...remember my caveats about signal handlers?
They apply.
--
http://www.catb.org/~esr/";>Eric S. Raymond
_
Amar Takhar :
> This also means we can remove the 'waf' binary from the Git repository and
> package it in with the tarball releases in the future.
I'd be opposed to this. It might compromise build replicability in the future.
--
http://www.catb.org/~esr/";>Eric S. Raymond
_
k...@roeckx.be said:
> Why do you set up a signal handler for this, and don't let the OS take care
> of it?
> Or alternativly, just call _exit() from the signal handler.
It's not trying to exit, just get out of a long running command.
ntpq has two long-running commands. (Maybe more.)
One is
k...@roeckx.be said:
> I want to add that it likely does at least something with the signal
> handlers so that it can time out.
You don't need signals to time out on network activity. Most reads/writes
have a timeout option. I forget the details. It's been a long time. If
that doesn't work
On Tue, Jan 26, 2016 at 11:03:01PM +0100, Kurt Roeckx wrote:
> > I haven't found anyplace in our code that messes with the signal mask. I
> > could easily be overlooking something that will be obvious in hindsight.
>
> Maybe getnameinfo() does.
I want to add that it likely does at least somethi
On Tue, Jan 26, 2016 at 01:38:52PM -0800, Hal Murray wrote:
>
> k...@roeckx.be said:
> > It's not clear to me when this longjmp() is called. But if changing to
> > siglongjmp() fixed it, it seems the signal handling got changed in between?
>
> It's called from the ^C signal handler. It's the b
k...@roeckx.be said:
> It's not clear to me when this longjmp() is called. But if changing to
> siglongjmp() fixed it, it seems the signal handling got changed in between?
It's called from the ^C signal handler. It's the brute force way of
terminating a command.
I haven't found anyplace in o
On Tue, Jan 26, 2016 at 01:07:04PM -0800, Hal Murray wrote:
>
> The problem is that somebody is masking off SIGINT. It works if I replace
> setjmp+longjmp with sigsetjmp+siglongjmp.
>
> The SIGINT handler was getting called with SIGINT masked off. That seems a
> bit strange. It was coming fr
The problem is that somebody is masking off SIGINT. It works if I replace
setjmp+longjmp with sigsetjmp+siglongjmp.
The SIGINT handler was getting called with SIGINT masked off. That seems a
bit strange. It was coming from deep within getnameinfo.
I haven't figured out if this is a bug in g
I've added a release mode to the build. The instructions are in the commit
message. This lowers the barrier for entry for using NTPSec and ensures our
tested versions work the same for the public.
I'll be enabling snapshots using BuildBot and uploading them to ftp.ntpsec.org
for users that wa
gha...@gmail.com said:
> 01-26T23:14:40 ntpd[28107]: error resolving pool hk.pool.ntp.org: No address
> associated with hostname (-5)
That tells you that DNS isn't working.
The pool stuff works for me.
Have you tried simple command line tools to verify that your DNS setup is
working? I use h
Mark Atwood :
> My lesson I take away from that is not that I am some special fount of
> valuable ideas, but that nearly everyone who works in the right parts of
> the tech space is, but that means little, as ideas are cheap, it's
> execution that is valuable.
I think this is *mostly* true. Occas
Re almost inventing DVCS and almost inventing Linux.
I keep a notebook list of ideas that I know I had, that I didnt have the
interest, realization, drive, time, or skills, to chase and execute on,
that within a year or two later had burst onto the scene as billion dollar
VC funded "awesome tech".
Sanjeev Gupta :
> Luckily, just before I did a victory dance, I checked out HEAD again; and
> did a waf configure; waf install . And I can no longer see the problem;
> all is well.
>
> > (And you *always* suspect tricky environmental factors when DNS lookups
> > are involved. That is, if you wer
On Wed, Jan 27, 2016 at 1:11 AM, Eric S. Raymond wrote:
> Well, yes, often. But...and I'm being serious now...it's good form to
> send a request for bisection back to the bug reporter when you suspect
> that the bug might be sensitive to environmental factors that are
> tricky to identify and re
Sanjeev Gupta :
> On Tue, Jan 26, 2016 at 11:41 PM, Eric S. Raymond wrote:
>
> > OK, here's where you gain a level in hackery. :-)
> >
> > Learn how to perform a git bisection (using Google to find a HOWTO) and
> > nail down which commit broke the lookup. Konowing that, it should be
> > easy to
Mark Atwood :
> Let me just chime in with... bisect is awesome.
>
> When I first did a bzr bisect about 8 years ago, I was delighted and
> peeved. Delighted because it's just so damn elegant, and peeved because
> it's something that could have been tooled for 15 years sooner, but
> generally was
On Wed, Jan 27, 2016 at 12:16 AM, Mark Atwood
wrote:
> > I thought the whole point of my using Open Source was that I complain,
> and you et al fix? :-)
>
> It is! However, you are one of the "et al". ;)
>
Drat! Foiled again.
Please see the two traces below:
>From ntpsec 0.9.1 (HEAD)
01-2
No, no, no...
It's "Given enough eyeballs, all bugs are shallow"[1]...
That is why Open Source is so good! No bugs!
...wait, why are there over 6600 FOSS projects on SCAN...
Uh, never mind...
1) ^ http://www.catb.org/esr/writings/homesteading/cathedral-bazaar/ar01s04.html
> On Jan 26, 2016,
> I thought the whole point of my using Open Source was that I complain,
and you et al fix? :-)
It is! However, you are one of the "et al". ;)
..m
On Tue, Jan 26, 2016 at 8:11 AM Sanjeev Gupta wrote:
>
> On Tue, Jan 26, 2016 at 11:41 PM, Eric S. Raymond wrote:
>
>> OK, here's where you ga
On Tue, Jan 26, 2016 at 11:41 PM, Eric S. Raymond wrote:
> OK, here's where you gain a level in hackery. :-)
>
> Learn how to perform a git bisection (using Google to find a HOWTO) and
> nail down which commit broke the lookup. Konowing that, it should be
> easy to fix.
>
Eric, I thought the wh
Let me just chime in with... bisect is awesome.
When I first did a bzr bisect about 8 years ago, I was delighted and
peeved. Delighted because it's just so damn elegant, and peeved because
it's something that could have been tooled for 15 years sooner, but
generally wasn't.
On Tue, Jan 26, 2016
Sanjeev Gupta :
> Sometime between 21 Jan and today, the following line in my ntp.conf
> pool hk.pool.ntp.org iburst
OK, here's where you gain a level in hackery. :-)
Learn how to perform a git bisection (using Google to find a HOWTO) and
nail down which commit broke the lookup. Konowing that, i
Hi,
Sometime between 21 Jan and today, the following line in my ntp.conf
pool hk.pool.ntp.org iburst
results in (ntpd.log)
01-26T23:14:40 ntpd[28107]: error resolving pool hk.pool.ntp.org: No
address associated with hostname (-5)
and (ntpq -pn)
root@ntpmon:~# ntpq -pn
remote refi
30 matches
Mail list logo
