On Wed, Jan 03, 2007 at 08:53:55AM -0500, Ben Wilson said:
> I managed to figure this out!
>
> Remember I have a nosuid, noexec /tmp partition to guard against
> possible file-upload vulnerabilities.
>
> I changed my ClamAV "TemporaryDirectory" to /var/clamav/tmp/ (which is
> not nosuid/noexec)
I managed to figure this out!
Remember I have a nosuid, noexec /tmp partition to guard against
possible file-upload vulnerabilities.
I changed my ClamAV "TemporaryDirectory" to /var/clamav/tmp/ (which is
not nosuid/noexec), and this solved the problem.
FYI - my inodes were fine, and I watch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Jan 02, 2007 at 10:41:21AM -0500, Ben Wilson wrote:
>LibClamAV Error: Cannot close file /tmp/clamav-29cad58e042679e3/main.fp.
>cli_untgz: No space left on device
>LibClamAV Error: cli_cvdload(): Can't unpack CVD file.
>LibClamAV Error: Can't l
On Tue, Jan 02, 2007 at 10:41:21AM -0500, Ben Wilson said:
> I'm running a RH 9 / Plesk server with Clamav version 0.88.7. Freshclam
> pulled down the new main.cvd (version 42) on 12/31/2006. Clamd
> immediately choked on it and I had to revert to the "stock" main.cvd
> that comes in the packa
I'm running a RH 9 / Plesk server with Clamav version 0.88.7. Freshclam
pulled down the new main.cvd (version 42) on 12/31/2006. Clamd
immediately choked on it and I had to revert to the "stock" main.cvd
that comes in the package. Subsequent tests have confirmed that the
daily.cvd pulled by
