SA3: Spamd forkbomb after syslog-ng restart?

23 Aug 2004 22:54:03 -0000 

        
        We're using syslog-ng 1.6.0rc3 and Perl 5.6.1 and SA 3 RC1, and have
found that the following sequence will cause a spamd fork bomb:

 1. Using the RH init script, start spamd (-d -x -u mail -D)
 2. Restart syslog-ng.
 3. Attempt to stop spamd with the RH init script.

        At this point the system becomes a spamd fork bomb.  We didn't see
this with SA 2.6.

        Is one of our packages (syslog-ng or perl) out of date?  Or is this
a real spamd bug?

 Thanks,
 Chris

Reply via email to