FreeBSD Port: clamav-0.87
Elijah Savage
esavage at digitalrage.org
Tue Sep 20 17:44:18 PDT 2005
Elijah Savage wrote:
> Elijah Savage wrote:
>
>> Michael L. Hostbaek wrote:
>>
>>> Jan Baggen (jbaggen) writes:
>>>
>>>
>>>> cc -DHAVE_CONFIG_H -I. -I. -I.. -I../clamd -I../libclamav -I../shared
>>>> -I/usr/local/include -D_THREAD_SAFE -O2 -pipe -funroll-loops
>>>> -march=pentiumpro -c clamav-milter.c
>>>> clamav-milter.c: In function `clamd_recv':
>>>> clamav-milter.c:3444: syntax error before `int'
>>>> clamav-milter.c:3448: `ret' undeclared (first use in this function)
>>>> clamav-milter.c:3448: (Each undeclared identifier is reported only
>>>> once
>>>> clamav-milter.c:3448: for each function it appears in.)
>>>> *** Error code 1
>>>>
>>>
>>>
>>>
>>> Simon just committed a fix for this. Please update your ports
>>> collection, and try again.
>>>
>>> /mich
>>>
>>> _______________________________________________
>>> freebsd-ports at freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>>> To unsubscribe, send any mail to
>>> "freebsd-ports-unsubscribe at freebsd.org"
>>>
>>>
>> After getting th new ports and doing a port upgrade I now get this
>> error in my maillog
>>
>> ClamAV-clamd: Can't connect to UNIX socket /var/run/clamav/clamd: No
>> such file or directory, retrying (1)
>> Sep 20 20:23:11 skywalker amavis[62435]: (62435-01) ClamAV-clamd:
>> Can't connect to UNIX socket /var/run/clamav/clamd: No such file or
>> directory, retrying (2)
>> Sep 20 20:23:17 skywalker amavis[62435]: (62435-01) ClamAV-clamd
>> av-scanner FAILED: Too many retries to talk to /var/run/clamav/clamd
>> (Can't connect to UNIX socket /var/run/clamav/clamd: No such file or
>> directory) at (eval 56) line 266.
>
>
> By the way I did restart all services including postfix after the
> upgrade.
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
Not sure why it is fixed now. But going back and doing a make deinstall
and them make reinstall seemed to have fixed this issue. I am not sure
why portupgrade did not work it did not give any errors at all.
More information about the freebsd-ports
mailing list