freebsd stable - Dec 2003 - strange log messages

Howdy, 

I just noticed these tonight after a cvsup/build
world/kernel/install world around 2am EST on the 8th
of dec.

Dec  9 02:14:23 fortytwo /kernel: issignal
Dec  9 02:16:17 fortytwo /kernel: issignal
Dec  9 02:17:50 fortytwo /kernel: issignal


after a man -k issignal  turned up nothing, I hit the
online manpages... 

http://www.freebsd.org/cgi/man.cgi?query=issignal&apropos=0&sektion=0&manpath=FreeBSD+4.9-stable&format=html

shows nothing either, the 5.x series... 
http://www.freebsd.org/cgi/man.cgi?query=issignal&apropos=0&sektion=0&manpath=FreeBSD+5.0-RELEASE&format=html

comes up with a page for it.

Question is, with a stable-supfile with *default
release=cvs tag=RELENG_4  and that message being
there, A) should the man page be with it, or B) should
/usr/src/UPDATING  have some mention of it?

Considering I can't code to save my life, what's up
here?



__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/

On Mon, 8 Dec 2003, jimmie james wrote:
> Howdy,
>
> I just noticed these tonight after a cvsup/build
> world/kernel/install world around 2am EST on the 8th
> of dec.
>
> Dec  9 02:14:23 fortytwo /kernel: issignal
> Dec  9 02:16:17 fortytwo /kernel: issignal
> Dec  9 02:17:50 fortytwo /kernel: issignal
This is being generated by this chunk of code from
src/sys/kern/kern_sig.c:

		case (int)SIG_IGN:
			/*
			 * Masking above should prevent us ever trying
			 * to take action on an ignored signal other
			 * than SIGCONT, unless process is traced.
			 */
			if ((prop & SA_CONT) == 0 &&
			    (p->p_flag & P_TRACED) == 0)
				printf("issignal\n");
			break;		/* == ignore */


So you have a process being traced that is getting ignored signals. I
suspect the message is a leftover debugging prinf and should be harmless.
You can file a PR to get this removed if you like.

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org