In the past, I've seen SIG11's happen for two other reasons... 1. Bad memory 2. Pushing an over-clocked machine faster than it's memory can handle.
Do either of these apply in this case? I mean, the upgrade to MD 2.48 might just be coincidental timing with a RAM stick that's about to fail altogether. Ken -----Original Message----- From: David F. Skoll [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 02, 2004 11:07 AM To: [EMAIL PROTECTED] Subject: Re: [Mimedefang] SIG11's with Mimedefang 2.48 On Tue, 2 Nov 2004, Martin Blapp wrote: > Have you seen this error too on older versions ? I just got it > once. Of course I I have not seen it, and it's very odd. > Nov 2 16:22:51 mx3 mimedefang[56969]: iA2FMXpa037602: Could not open > MIMEDefang 2.48 on 192.168.0.1/COMMANDS: No such file or directory It looks like the scan directory is being overwritten by "MIMEDefang 2.48 on 192.168.0.1", which makes no sense whatsoever.. Could it be a FreeBSD-specific issue? A bug in pthreads? The code that generates "MIMEDefang 2.48 on 192.168.0.1" is around line 1431 of mimedefang.c, and I see no way that it can overwrite data->dir (which is what appears to be happening.) Anyone else seeing this? Regards, David. _______________________________________________ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang _______________________________________________ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
