Hi, On Sun, Feb 15, 2009 at 22:39, Sébastien Aperghis-Tramoni <sebast...@aperghis.net> wrote:
>> In the fwknopd code, this happens when calling iptables, which >> triggers >> a SIGCHLD on exit, but can happen with any signal. > > I can't reproduce the problem using your test case, either with > Net::Pcap 0.16 on OSX, Net::Pcap 0.04 or 0.16 on Debian etch x86. I've been working with Net::Pcap 0.16 on Debian sid, which means: libpcap0.8 0.9.8-5 perl 5.10.0-19 I wouldn't surprise me if changes in the versions of any of these would produce different results. >> Meanwhile this is solved, see the attached patch that's useful as a >> workaround for fwknopd > > Is this patch reversed? The destination already looks like the > version of fwknopd I downloaded (1.9.10). > If that's the case, I'm not sure to understand how this fixes the > problem. Yes, sorry, see my other patch I've sent to the bug report.This was reversed and incorrect. The workaround was just to use a minimum callback that saves the values and then call the other routines (which trigger a SIGCHLD) outside of the callback.. -- Martín Ferrari -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
