Noob education time... 1. Do what the message says - read the man page it references
2. Look at docs/FAQ: Q. "application bug: ntop(...) has SIGCHLD set to SIG_IGN but calls wait(). (See the NOTES section of 'man 2 wait'). Workaround activated." This message and the NOTES section of the man page lead me to believe that the problem is handled but the kernel feels the need to report it from time to time. A. Read the NOTES section. The problem has been handled, but the kernel feels the need to report it from time to time. See the article at http://article.gmane.org/gmane.linux.ntop.general/5304 3. You can always search the back traffic @ Gmane... -----Burton > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of > Dunlop, Sean > Sent: Tuesday, December 23, 2003 10:31 PM > To: [EMAIL PROTECTED] > Subject: [Ntop] Syslog Kernel messages? > > > > I am a total noob so please no flames :-) > > Im getting the following syslog message on my Redhat 9 NTOP box. > Ive read the 'man 2 wait' notes and it doesnt help me to > understand if this can be ignored or fixed or whatever? > > Dec 24 12:24:10 netmon01 kernel: application bug: ntop(3688) has > SIGCHLD set to SIG_IGN but calls wait(). > Dec 24 12:24:10 netmon01 kernel: (see the NOTES section of 'man 2 > wait'). Workaround activated. > > What should/can I do about it? > > _______________________________________________ > Ntop mailing list > [EMAIL PROTECTED] > http://listgateway.unipi.it/mailman/listinfo/ntop > _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
