On Sun, 2007-10-21 at 17:19 -0700, Todd A. Jacobs wrote:
> On Sat, Oct 20, 2007 at 11:30:52PM -0400, David Clymer wrote:
>
> > Have you checked to ensure that clamd is, in fact, running? If not, it
>
> Uh...yes. See above, where I said that piping an individual file to
> clamdscan works. :)
Err.
On Sat, Oct 20, 2007 at 11:30:52PM -0400, David Clymer wrote:
> Have you checked to ensure that clamd is, in fact, running? If not, it
Uh...yes. See above, where I said that piping an individual file to
clamdscan works. :)
--
"Oh, look: rocks!"
-- Doctor Who, "Destiny of the Daleks"
-
On Sat, 2007-10-20 at 14:51 -0700, Todd A. Jacobs wrote:
> I'm getting the following error with clamdscan:
>
> $ formail -ds < $MAIL | clamdscan --disable-summary --stdout -
> WARNING: Can't write to the socket.
>
> Clamscan works fine, and so does piping an individual file into
> clamdsc
I'm getting the following error with clamdscan:
$ formail -ds < $MAIL | clamdscan --disable-summary --stdout -
WARNING: Can't write to the socket.
Clamscan works fine, and so does piping an individual file into
clamdscan, so there seems to be a problem with clamdscan and larger
pipes. Wha
This one time, at band camp, John Fleming said:
>
> - Original Message -
> From: "John Fleming" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, July 18, 2004 10:14 PM
> Subject: [Clamav-users] Clamdscan Error 2
>
>
>
On Mon, 19 Jul 2004 at 7:38:56 -0500, John Fleming wrote:
> - Original Message -
> From: "John Fleming" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, July 18, 2004 10:14 PM
> Subject: [Clamav-users] Clamdscan Error 2
>
> > C
- Original Message -
From: "John Fleming" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, July 18, 2004 10:14 PM
Subject: [Clamav-users] Clamdscan Error 2
> ClamAV (clamd) was working fine until I updated Debian unstable today.
Now
> I'm gett
7 matches
Mail list logo
