Date: Fri, 4 Jul 2014 14:40:57 +0200 From: Marko =?UTF-8?B?Q3VwYcSH?= <marko.cupac@mimar.rs> To: Andrea Venturoli <ml@netfence.it> Cc: mm@FreeBSD.org, freebsd-ports@freebsd.org Subject: Re: Latest c-icap update Message-ID: <20140704144057.c0c29ba0a9b10968ddcfaaaa@mimar.rs> In-Reply-To: <53B68E11.10905@netfence.it> References: <53B68E11.10905@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 04 Jul 2014 13:20:49 +0200 Andrea Venturoli <ml@netfence.it> wrote: > I see lots of bug reports on the net wrt to c-icap on FreeBSD and > signal 11; however I believe they are all referring to old, now > solved, problems. Is it so? Those are probably mostly mine. I can't get squidclamav get to work on 10.0 without exiting on signals 10 and 11. I had a correspondence in March directly with Gilles Darold, author of squidclamav. He was helpful, sending me experimental code for testing, but finally instructed me to "use a Linux distribution instead I think you will be more sure to have a working solution", until he figures things out. Since then, I am monitoring ports for new versions of c-icap and squidclamav, update every time new port is out, enable squidclamav in squid configuration only to see it crashing after a few minutes, then disabling it back. My PR opened here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D190336 --=20 Marko Cupa=C4=87
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140704144057.c0c29ba0a9b10968ddcfaaaa>