Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site iuvax.UUCP Path: utzoo!watmath!clyde!floyd!harpo!ihnp4!inuxc!iuvax!saj From: saj@iuvax.UUCP Newsgroups: net.unix-wizards Subject: what is issig (4.1bsd) - (nf) Message-ID: <161@iuvax.UUCP> Date: Wed, 15-Feb-84 15:37:00 EST Article-I.D.: iuvax.161 Posted: Wed Feb 15 15:37:00 1984 Date-Received: Fri, 17-Feb-84 02:21:37 EST Sender: saj@iuvax.UUCP Organization: Indiana U, Bloomington Lines: 38 #N:iuvax:1200003:000:1320 iuvax!vahe Oct 19 15:30:00 1983 I need clarification on a strange thing that's been happening to my 11/780 running 4.1BSD (unmodified). Lately, the word "issig" has been printing on the console in voluminous quantities. Nothing else, just the word on a single line: "issig". Reading through /sys/sys/sig.c, I find that issig() is a function which returns true if the current process has a signal to process. It contains the following code: for(;;) { /* note: breaks when no more signals */ ... ... switch (u.u_signal[sig]) /* note: sig is the current signal */ ... ... case SIG_HOLD: case SIG_IGN: if ((p->p_flag&STRC) == 0) printf("issig\n"); continue; ... ... } Not having earned my wizard's stripes yet, this code has been impervious to my trying to figure it out. Why the printf? Why can't that situation just be ignored -- after all, that's what the continue will make it do: go to the beginning of the loop and look for the next signal. Can someone in the know (please -- no guesses) enlighten me? Do I need to worry about this situation? What's causing it, anyway? Just what is that piece of code doing?? Many thanks, Vahe Sarkissian UUCP : {ihnp4 | ihnss}!inuxc!iuvax!vahe CSNET: Vahe@Indiana