We've discussed this in the past - AFAIR nobody ever really figured out what RH means. There's no specific POSIX limitation, etc., but it could be that EL3 is finally enforcing whatever that warning means.
I don't have EL3, so I can't test in that environment. -----Burton > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of > Mitesh P Choksi > Sent: Tuesday, August 31, 2004 3:28 PM > To: [EMAIL PROTECTED] > Subject: [Ntop] killed by SIGSEGV > > > Dear All, > > I am having ntop dying in a few minutes of starting. > > I use WhiteBox Linux EL3 which is based on RedHat EL 3.0 > > dmesg after ntop dies shows the following: > application bug: ntop(20149) has SIGCHLD set to SIG_IGN but calls wait(). > (see the NOTES section of 'man 2 wait'). Workaround activated. > device eth0 left promiscuous mode > > strace -p <pid> shows the following: > rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0 > rt_sigaction(SIGCHLD, NULL, {SIG_IGN}, 8) = 0 > nanosleep({10, 0}, 0xbfffb054) = -1 EINTR (Interrupted > system call) > +++ killed by SIGSEGV +++ > > I turned on debugging (-K) but don't get any hints from /var/log/messages. > > I have tried googling but have not found any specific answer. I need to > know how to I go around troubleshooting current ntop problem. > > Thanking you in advance. > > Regards, > > Cyberdude Murli > Land of the Kilimanjaro > The World! > _______________________________________________ > Ntop mailing list > [EMAIL PROTECTED] > http://listgateway.unipi.it/mailman/listinfo/ntop _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
