>>>>> "Burton" == Burton M Strauss, <Burton> writes:
Burton> I'll look into it, but you're probably right about just
Burton> using the same code. However, it's not the same situation,
Burton> as the rrd plugin doesn't run a web server. The extant web
Burton> server (which already has the SIGPIPE handler) is what feeds
Burton> the requests into the rrd plugin. So the SIGPIPEs are being
Burton> generated by some other situation.
I haven't spent any time working on multi-threaded code on Linux, but a
few years back did some extensive work with threads on an old version of
LynxOS. In that system, any thread that defined a handler for a signal
could receive an instance of that signal, even if it really didn't have
anything to do with that thread. Is that same model valid here? if so,
the very fact the the rrdPlugin sets a handler for SIGPIPE makes it
liable to receive one, even if it doesn't make sense.
Burton> Please collect and post the gdb backtraces (bt full, plus
Burton> some judicious frame n and list commands).
I hope to have some later this week to look at this for you, but "Real
Work" is intruding too much lately.
--
David L. Kindred
Unix Systems & Network Administrator
Telesciences, Inc.
2000 Midlantic Drive, Suite 410
Mt. Laurel, NJ 08054-1512, USA
Office: +1 856 642 4184
Fax: +1 856 866 0185
Mobile: +1 609 332 6450
[EMAIL PROTECTED]
www.edbtelesciences.com
_______________________________________________
Ntop-dev mailing list
[EMAIL PROTECTED]
http://listgateway.unipi.it/mailman/listinfo/ntop-dev
