Hi,
on my vm running Suse10.0 i can't reproduce this.
Regards,
Arne
Sam Clippinger schrieb am 15.10.2008 03:17:
I forgot to ask earlier -- when you activated full logging, were any log
files actually produced? If I could see them, they would probably be
very helpful in tracking this
You could try running a debug build of spamdyke (unstripped binary,
remote the strip command from Makefile) and attach gdb or strace to a
process (id) that is eating up all cpu. That should help Sam to find
what the problem is.
Note that debug builds have a larger memory footprint, so you might
Hi,
forgot not all of you are software developers, so added some explanation
of how to extract a useable backtrace from a running process with gdb.
Am 15.10.2008 8:27 Uhr, Felix Buenemann schrieb:
You could try running a debug build of spamdyke (unstripped binary,
remote the strip command from
Sam,
There is a set of POSIX compatible regular expression functions available in
C. The functions regcomp() and regexec() are both used by qmail to provide
regexp testing for the control/badx files.
Regards,
Tim
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
Yes, me also. Looks like this is one of the reasons, why Linux-tools
are mostly
developped for specific systems, when making RPM's. So Spamdyke 4.0.5 seems
to be good for SuSE's, and maybe not on others? Just quick shot from me^^ :)
Arne Metzger schrieb:
Hi,
on my vm running Suse10.0 i can't
Hi Sam,
Will that also solve the issue of smtp errors on the client-side? I
couldn't find any log for those customers who had those errors, not
even in the syslog. I did copy the error tho, if that may be of any
help. Can reproduce that anytime too.
And just to correct myself earlier, its
One of my customers reported a problem like this, he could not send a
message of 23MB.
Outlook Express View the error code: 0x800ccc0f
2008/10/15 Arthur Girardi [EMAIL PROTECTED]:
Hi Sam,
Will that also solve the issue of smtp errors on the client-side? I
couldn't find any log for those
Free BSD 6.0 release p16
spamdyke 4.0.5
created /usr/local/spamdyke dir
tar -xzvf filename
ran ./configure - completed (no errors until make, see snapshot below)
checking for library containing getopt_long... none required
checking whether anonymous inner functions are supported by default...
gcc segfaults on FreeBSD 6.0/i386 when compiling spamdyke.
I have the port marked as broken for FreeBSD = 6.0
-Peter
[EMAIL PROTECTED] wrote, On 10/15/2008 12:04 PM:
Free BSD 6.0 release p16
spamdyke 4.0.5
created /usr/local/spamdyke dir
tar -xzvf filename
ran ./configure - completed (no
This came up a couple of weeks ago also:
http://www.mail-archive.com/spamdyke-users@spamdyke.org/msg01635.html
gcc is crashing, not spamdyke, so even if there were something I could
do to fix it, I don't know where to start.
-- Sam Clippinger
Peter Kieser wrote:
gcc segfaults on FreeBSD
I understand. Somebody I know is running spamdyke v3.18 under Free BSD 6.0
successfully.
Can I download v3.18 somewhere?
Tks!
Darren.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sam Clippinger
Sent: Wednesday, October 15, 2008 15:46
To: spamdyke
Hi Darren Peter,
I looked into this issue and found a simple fix: Simply by creating a
preprocessed source and then running gcc on that preprocessed source
will avoid the compiler crash.
Please try the attached patch on a clean source of the latest spamdyke
release. Be sure to remove Makefile
Hi Shantanu,
please try the attached patch and see if it fixes your problem.
-- Felix Buenemann
Am 02.10.2008 8:24 Uhr, K. Shantanu schrieb:
Hello,
I am trying to build spamdyke-4.0.4 on FreeBSD 6.2 with gcc 3.4.6.
./configure works fine but make fails.
# make
gcc -Wall -O2
Excellent work! I'll get a FreeBSD 6.0 test machine installed so I can
incorporate this change permanently into spamdyke's Makefile.
-- Sam Clippinger
Felix Buenemann wrote:
Hi Darren Peter,
I looked into this issue and found a simple fix: Simply by creating a
preprocessed source and then
14 matches
Mail list logo
