On 09/01/2019 00:01, Joel Esler (jesler) wrote:
Solaris is definitely not one of the OSs in our build farm. Just FYI.
Oh, I'm not surprised about that, I can't even attempt to justify you
having an x64 VM set-up to build clamav, given that the set of Solaris
clamav users may be no greater
Hi Alan,
It sounds like your system defaults to having the -Wall and -Wextra compiler
flags enabled. We do indeed still have a lot of work to clean up warnings when
building with -Wall and -Wextra, I certainly want to clean up all the warnings
long term, but the other remaining ones are, to
On Wed, 9 Jan 2019, Micah Snyder (micasnyd) wrote:
> Hi Alan,
>
> It sounds like your system defaults to having the -Wall and -Wextra
> compiler flags enabled. We do indeed still have a lot of work to
> clean up warnings when building with -Wall and -Wextra, I certainly
> want to clean up all
clamav-0.101.0-3.fc29.x86_64
clamd-0.101.0-3.fc29.x86_64
clamav-milter-0.101.0-3.fc29.x86_64
sendmail-8.15.2-29.fc29.x86_64
4.19.13-300.fc29.x86_64
Milter (clamav-milter): write(D) returned -1, expected 23: Broken pipe
Also seeing errors like:
clamd[25994]: LibClamAV Error:
>
> sm-client.service: Failed to parse PID from file /run/sm-client.pid:
> Invalid argument
>
> I'm not too familiar with sendmail client, so I'll defer this to someone
> else more knowledgeable.
>
A bug that won't get fixed?
https://bugzilla.redhat.com/show_bug.cgi?id=748171
Anyways any idea
Hi Robert,
LibClamAV Error: cli_get_filepath_from_filedesc: File path for fd [10] is:
/tmp/clamav-f71a825e6280ce33121e5fdc8578591a.tmp
The above is not actually an error. In 0.101.1 we have already changed it to be
a debug level message instead. Sorry about the confusion.
sm-client.service:
