[ntp:questions] signal_no_reset: signal 18 had flags 20000

2010-12-14 Thread bombjack
I have STFI like crazy, but can't find an explanation for the error
code signal_no_reset: signal 18 had flags 2 Could someone
explain what this mean? Or even better, give me a hint where I can
find info about all these error codes etc for ntp

Regards,
Fredrik

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions


Re: [ntp:questions] signal_no_reset: signal 18 had flags 20000

2010-12-14 Thread Dave Hart
On Tue, Dec 14, 2010 at 20:58 UTC, bombjack bombjac...@gmail.com wrote:
 I have STFI like crazy, but can't find an explanation for the error
 code signal_no_reset: signal 18 had flags 2 Could someone
 explain what this mean?

That is a harmless overly-chatty diagnostic message that is no longer
generated by the latest ntpd.  signal_no_reset() is changing the
signals which are enabled and generates the warning if the prior flags
contain a bit the code didn't recognize.  Newer ntpd recognizes and
silently ignores the flag, I forget what the symbolic name is.

Cheers,
Dave Hart
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions


Re: [ntp:questions] signal_no_reset: signal 18 had flags 20000

2010-12-14 Thread Harlan Stenn
 I have STFI like crazy, but can't find an explanation for the error
 code signal_no_reset: signal 18 had flags 2 Could someone
 explain what this mean? Or even better, give me a hint where I can
 find info about all these error codes etc for ntp

It's not an error, it is information.

In libntp/syssignal.c, there is a function called 'signal_no_reset',
which we call in order to set up the flags we expect to see for a
given signal.

As I recall, we handle all of the cases we know about/expect.

If, after handling all of the signal flags we know about, we discover
there are *other* flags still set, we simpy announce those flags.

You should be able to look at the documentation for your sigaction()
system call and in somewhere like /usr/include/sys/signal.h and see what
flag has the value 0x2.

H
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions


Re: [ntp:questions] signal_no_reset: signal 18 had flags 20000

2010-12-14 Thread Hal Murray
In article 67578d3d-adff-469a-a57b-a9ff54460...@39g2000yqa.googlegroups.com,
 bombjack bombjac...@gmail.com writes:
I have STFI like crazy, but can't find an explanation for the error
code signal_no_reset: signal 18 had flags 2 Could someone
explain what this mean? Or even better, give me a hint where I can
find info about all these error codes etc for ntp

Most ntpd error/syslog messages come from a call to msyslog which
has printf type arguments.

If you have the sources handy, you can grep for part of the text
from the error message.  In this case,
  grep signal_no_reset: signal . -r
gets one hit in ./libntp/syssignal.c

Note that it helps to have the sources that correspond to the code
you are running.  You can get that either by tracking down the sources
for the code you are running, or grabbing a known source and rebuilding
and installing.
  http://support.ntp.org/bin/view/Main/SoftwareDownloads

-- 
These are my opinions, not necessarily my employer's.  I hate spam.

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions


Re: [ntp:questions] signal_no_reset: signal 18 had flags 20000

2010-12-14 Thread David Woolley

bombjack wrote:

I have STFI like crazy, but can't find an explanation for the error
code signal_no_reset: signal 18 had flags 2 Could someone
explain what this mean? Or even better, give me a hint where I can
find info about all these error codes etc for ntp


I'd start with the man page for signal.  It looks like this message is 
leaving little to the imagination.  You may also need to look at the 
relevant files in /usr/linclude/...


On Linux, signal 18 is likely to be SIGCONT, which doesn't seem a 
particularly legitimate one for ntpd to be receiving, as you wouldn't 
normally run it in a way in which it could get stopped.


If you are not doing something strange, this is likely to be a low level 
platform compatibility issue, for which you will need to be able to 
understand the source code.


___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions