Thank you for the detail here.  Unfortunately, I had already done much of
that.  ldd confirms that both clamd and freshclam are linked to
/usr/local/lib/libclamav.so.1

When I shut down clamd and freshclam, move that library out, and try to
restart, both clamd and freshclam bomb out saying the library is not
found.

I have verified that LD_LIBRARY_PATH isn't sending it to another location,
and even if it were, there does not exist another libclamav for it to use.

Likewise, I have run strings on all libraries in /usr/local/lib and
/usr/lib looking for the string 0\.81 and have only found
/usr/local/lib//usr/local/lib/libclamav.so.1.

My next step is to try to run them inside truss to see what files it is
referencing (I think I will likely have to recompile with symbols
retained, though).

I know this is a common problem that crops up, but what I'm seeing isn't
matching up with any of the problems that have come up in the archives so
far.

At version 0.81, did libclamav.so.1 exist as a different name and not have
the version number built in?

Many thanks for the help!

Jerry

> Jerry - somewhere in your library path is an earlier version of the clamav
> library. This is very common. In the bin path of the user that clamav runs
> as there may even be an old executable. You need to run what ever tools
> are available to you to locate it/them. In Solaris you can use the ldd
> command against the binary that is popping up the error. You can expand
> LD_LIBRARY_PATH (a particularly evil env var) and manually walk that. This
> needs to be explored as the user your clamav runs as (hence the evil
> nature of LD_LIBRARY_PATH). Somewhere you are going to find a lib file
> that is wrong.
>

>


_______________________________________________
http://lurker.clamav.net/list/clamav-users.html

Reply via email to