On Mon, Oct 4, 2010 at 4:24 PM, Jerry wrote:
> On Mon, 4 Oct 2010 16:12:09 +0300
> Odhiambo Washington articulated:
>
> > Oddly enough, after doing a pkg_delete -dfv clamav\* (I'm in bash)
> > and then doing 'portinstall -N clamav' (I already have the config I
> > use so no need for make config
I have FreeBSD 8.1-STABLE. I have just updated from 0.96.2 to 0.96.3 and now
clamd won't start, giving segfault.
ct 4 11:06:11 mail kernel: pid 45864 (clamd), uid 26: exited on signal 11
Oct 4 11:06:22 mail kernel: pid 45917 (clamd), uid 26: exited on signal 11
Oct 4 11:06:30 mail kernel: pid 4
On Mon, 4 Oct 2010 13:12:28 +0300
Odhiambo Washington articulated:
> I have FreeBSD 8.1-STABLE. I have just updated from 0.96.2 to 0.96.3
> and now clamd won't start, giving segfault.
>
> ct 4 11:06:11 mail kernel: pid 45864 (clamd), uid 26: exited on
> signal 11 Oct 4 11:06:22 mail kernel: pi
2010/10/4 Török Edwin
> On Mon, 4 Oct 2010 16:12:09 +0300
> Odhiambo Washington wrote:
>
> > On Mon, Oct 4, 2010 at 2:25 PM, Jerry
> > wrote:
> >
> > > On Mon, 4 Oct 2010 13:12:28 +0300
> > > Odhiambo Washington articulated:
> > >
> > > > I have FreeBSD 8.1-STABLE. I have just updated from 0.9
On Mon, 4 Oct 2010 16:12:09 +0300
Odhiambo Washington wrote:
> On Mon, Oct 4, 2010 at 2:25 PM, Jerry
> wrote:
>
> > On Mon, 4 Oct 2010 13:12:28 +0300
> > Odhiambo Washington articulated:
> >
> > > I have FreeBSD 8.1-STABLE. I have just updated from 0.96.2 to
> > > 0.96.3 and now clamd won't st
On Mon, Oct 4, 2010 at 2:25 PM, Jerry wrote:
> On Mon, 4 Oct 2010 13:12:28 +0300
> Odhiambo Washington articulated:
>
> > I have FreeBSD 8.1-STABLE. I have just updated from 0.96.2 to 0.96.3
> > and now clamd won't start, giving segfault.
> >
> > ct 4 11:06:11 mail kernel: pid 45864 (clamd), ui
On Mon, 4 Oct 2010 16:12:09 +0300
Odhiambo Washington articulated:
> Oddly enough, after doing a pkg_delete -dfv clamav\* (I'm in bash)
> and then doing 'portinstall -N clamav' (I already have the config I
> use so no need for make config), clamd has now started fine.
I use Bash too. However, I
On Mon, 4 Oct 2010 13:12:28 +0300
Odhiambo Washington wrote:
> I have FreeBSD 8.1-STABLE. I have just updated from 0.96.2 to 0.96.3
> and now clamd won't start, giving segfault.
>
> ct 4 11:06:11 mail kernel: pid 45864 (clamd), uid 26: exited on
> signal 11 Oct 4 11:06:22 mail kernel: pid 4591
On Mon, Oct 4, 2010 at 2:25 PM, Jerry wrote:
> On Mon, 4 Oct 2010 13:12:28 +0300
> Odhiambo Washington articulated:
>
> > I have FreeBSD 8.1-STABLE. I have just updated from 0.96.2 to 0.96.3
> > and now clamd won't start, giving segfault.
> >
> > ct 4 11:06:11 mail kernel: pid 45864 (clamd), ui
On 10/1/10 11:30 PM, Al Varnell wrote:
On 10/1/10 12:07 AM, "Dennis Peterson" wrote:
A short term solution until Apple updates bzip2 is to install MacPorts if not
already installed, and use it to install bzip2. It will install it in
/opt/local
so you need to add an option to your clamav config
omonte7 wrote:
>
> Hello, I want to get some recommendations on setting MaxFileSize and
> MaxScanSize. I'm using clamav for local file scanning only, no email
> scanning. The clamd.conf man pages says the following for each of these
> settings:
> "Warning: disabling this limit or setting i
On 10/4/10 7:51 AM, "Dennis Peterson" wrote:
> On 10/1/10 11:30 PM, Al Varnell wrote:
>> On 10/1/10 12:07 AM, "Dennis Peterson" wrote:
>>
>>> A short term solution until Apple updates bzip2 is to install MacPorts if
>>> not
>>> already installed, and use it to install bzip2. It will install it
On 10/4/10 9:20 AM, Al Varnell wrote:
On 10/4/10 7:51 AM, "Dennis Peterson" wrote:
On 10/1/10 11:30 PM, Al Varnell wrote:
On 10/1/10 12:07 AM, "Dennis Peterson" wrote:
A short term solution until Apple updates bzip2 is to install MacPorts if
not
already installed, and use it to install bz
On 04/10/10 18:25, Dennis Peterson wrote:
> On 10/4/10 9:20 AM, Al Varnell wrote:
>> On 10/4/10 7:51 AM, "Dennis Peterson" wrote:
>>
>>> On 10/1/10 11:30 PM, Al Varnell wrote:
On 10/1/10 12:07 AM, "Dennis Peterson" wrote:
> A short term solution until Apple updates bzip2 is to inst
On 10/4/10 9:39 AM, "Erwan David" wrote:
> On 04/10/10 18:25, Dennis Peterson wrote:
>> On 10/4/10 9:20 AM, Al Varnell wrote:
>>> On 10/4/10 7:51 AM, "Dennis Peterson" wrote:
>>>
On 10/1/10 11:30 PM, Al Varnell wrote:
> On 10/1/10 12:07 AM, "Dennis Peterson" wrote:
>
>> A sh
*
Hi,
I'm having problems building 0.96.3 on Solaris 9 and 10. I believe I've
copied in the appropriate sections of configure and make below. Can anyone
tell me why this might be failing? Or, what other information I can provide
that might help?
Thanks,
Tom
>From configure:
checking whether
On Mon, Oct 4, 2010 at 8:28 PM, Tom Goerger wrote:
> I'm having problems building 0.96.3 on Solaris 9 and 10. I believe I've
> copied in the appropriate sections of configure and make below. Can anyone
> tell me why this might be failing? Or, what other information I can provide
> that might he
On 10/4/2010 1:28 PM, Tom Goerger wrote:
> I'm having problems building 0.96.3 on Solaris 9 and 10. I believe I've
> copied in the appropriate sections of configure and make below. Can anyone
> tell me why this might be failing? Or, what other information I can provide
> that might help?
What
We're using gcc to compile. No parameters on configure. The same setup was
used to compile 0.95.2 just fine, without any problems, but it's bailing
here without giving me a reason that I can decipher, at least.
On Mon, Oct 4, 2010 at 2:19 PM, René Berber wrote:
> On 10/4/2010 1:28 PM, Tom Goer
On 10/4/2010 2:24 PM, Tom Goerger wrote:
> We're using gcc to compile. No parameters on configure. The same setup was
> used to compile 0.95.2 just fine, without any problems, but it's bailing
> here without giving me a reason that I can decipher, at least.
When you get a "cannot run C++ compil
On 10/4/10 10:03 AM, Al Varnell wrote:
On 10/4/10 9:39 AM, "Erwan David" wrote:
On 04/10/10 18:25, Dennis Peterson wrote:
On 10/4/10 9:20 AM, Al Varnell wrote:
On 10/4/10 7:51 AM, "Dennis Peterson" wrote:
On 10/1/10 11:30 PM, Al Varnell wrote:
On 10/1/10 12:07 AM, "Dennis Peterson"w
On Oct 4, 2010, at 5:08 PM, Dennis Peterson wrote:
> On 10/4/10 10:03 AM, Al Varnell wrote:
>> On 10/4/10 9:39 AM, "Erwan David" wrote:
>>
>>> On 04/10/10 18:25, Dennis Peterson wrote:
On 10/4/10 9:20 AM, Al Varnell wrote:
> On 10/4/10 7:51 AM, "Dennis Peterson" wrote:
>
>>
On 10/4/10 6:03 PM, Al Varnell wrote:
I troubleshoot ClamXav for users and it's important for me to not get ahead
of the ClamXav developer or Apple, so I must leave things as they are until
Mark has a chance to compile and release 0.96.3 and or Apple gets around to
fixing bzip2.
I just don't
On 10/4/10 6:10 PM, "Dennis Peterson" wrote:
> On 10/4/10 6:03 PM, Al Varnell wrote:
>
>>>
>> I troubleshoot ClamXav for users and it's important for me to not get ahead
>> of the ClamXav developer or Apple, so I must leave things as they are until
>> Mark has a chance to compile and release 0.
On 10/4/10 6:25 PM, Al Varnell wrote:
otool gives me identical results
I've got a PPC so I'm still at Leopard 10.5.8.
$ ls -l *bz2*
-rwxr-xr-x 1 root wheel 282048 Nov 11 2008 libbz2.1.0.4.dylib
-rwxr-xr-x 1 root wheel 282048 Jun 17 2009 libbz2.1.0.5.dylib
lrwxr-xr-x 1 root wheel
On 10/4/10 6:52 PM, "Dennis Peterson" wrote:
> On 10/4/10 6:25 PM, Al Varnell wrote:
>
>> otool gives me identical results
>>
Sorry, I guess I should have said it's identical to yours:
Load command 9
cmd LC_LOAD_DYLIB
cmdsize 52
name /usr/lib/libbz2.1.0.dylib (offset 2
On 10/4/10 8:29 PM, Al Varnell wrote:
Could it be that clamd was somehow compiled with 1.0.2?
It appears that your library is 1.0.2 regardless of what the binary might be.
Did you ever do a restore of you /lib? That's most frequently how libs get
mysteriously backleveled. Assuming it was ever
27 matches
Mail list logo