http://bugzilla.spamassassin.org/show_bug.cgi?id=3059
------- Additional Comments From [EMAIL PROTECTED] 2004-04-29 11:32 -------
Subject: Re: runaway spamd with pyzor (uses 100% CPU and does not return)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[EMAIL PROTECTED] writes:
> I've only tested against last stable 2.63 because 3.0.0 isn't released yet.
> Regarding your questions:
> * Yes, I've done a 'pyzor discover'. Please note that pyzor works with
> spamassassin and only _some_ (not all) messages make spamd hang.
> A sample message is provided at the given URL.
Yep, I tested with that msg and it failed to hang for me.
> * The command line is included at the very top of the debug logfiles
> (again available from the specified URL above)
ah, sorry, didn't spot that. OK, re-running:
cd (builddir)/t
mkdir /tmp/spamd
/usr/bin/perl -T -w ../spamd/spamd -D --debug --max-children=10
--pidfile=./spamd.pid --paranoid --auto-whitelist --create-prefs --user-config
--siteconfigpath=/etc/mail/spamassassin --helper-home-dir=/tmp/spamd
--socketpath=./spamd.socket &
../spamc/spamc -U ./spamd.socket < ~/DL/spam-testmsg
../spamc/spamc -U ./spamd.socket < ~/DL/spam-testmsg
../spamc/spamc -U ./spamd.socket < ~/DL/spam-testmsg
../spamc/spamc -U ./spamd.socket < ~/DL/spam-testmsg
../spamc/spamc -U ./spamd.socket < ~/DL/spam-testmsg
seems to be working fine with 3.0.0.... I did notice that the first run
did a pyzor discover, BTW, since the pyzor config file it uses is in the
helper-home-dir ("/tmp/spamd" in this case). But that worked fine.
So I'm not able to reproduce it so far.
- --j.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFAkUoTQTcbUG5Y7woRArnKAJ4pq/gsrzLutywyui45/p8X8ReXPwCbB1y0
SE+qnctK0NmVEQcjaDLxaCE=
=+reD
-----END PGP SIGNATURE-----
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
