## Török Edwin (ed...@clamav.net):
> I think I got it:
> off_t st_size;/* total size, in bytes */
>
> The st_size member of the stat buffer is a signed value, so any file over 2GB
> in size
> would be negative. stat() won't allow that so instead it returns an error
> telling
Hey, Edwin!
Am 14.10.2011 15:19, schrieb Török Edwin:
On 10/14/2011 04:13 PM, Simon Friedberger wrote:
Does it print an error?
Yes, it does.
stat failed: Value too large for defined data type
Now what does that mean? :)
I think I got it:
off_t st_size;/* total size, in
On 10/14/2011 04:13 PM, Simon Friedberger wrote:
>> Does it print an error?
> Yes, it does.
> stat failed: Value too large for defined data type
> Now what does that mean? :)
>
I think I got it:
off_t st_size;/* total size, in bytes */
The st_size member of the stat buffer is
Am 14.10.2011 11:42, schrieb Török Edwin:
On 10/14/2011 12:30 PM, Simon Friedberger wrote:
Hi, Edwin!
On 14.10.2011 11:02, Török Edwin wrote:
On 10/14/2011 11:49 AM, Simon Friedberger wrote:
It seems that this error can be caused by different problems like a wrong inode
number when mounting
On 10/10/2011 5:28 AM, Matus UHLAR - fantomas wrote:
On 9/30/2011 10:56 PM, Nathan Gibbs wrote:
clamscan itself isn't that smart, but if you are using unix, find could
feed a list of things to clamscan.
On 03.10.11 11:34, Bowie Bailey wrote:
>Just keep in mind that it is quite easy to arbitra
On 10/14/11 2:24 AM, "Simon Friedberger" wrote:
> There is nothing related to filesize in /etc/clamav/clamd.conf
Mine says:
##
## Limits
##
# The options below protect your system against Denial of Service attacks
# using archive bombs.
# This option sets the maximum amount of data to be scann
On 10/14/2011 12:30 PM, Simon Friedberger wrote:
> Hi, Edwin!
>
> On 14.10.2011 11:02, Török Edwin wrote:
>> On 10/14/2011 11:49 AM, Simon Friedberger wrote:
>>>
>>> It seems that this error can be caused by different problems like a wrong
>>> inode number when mounting CIFS or very large files.
Hi, Edwin!
On 14.10.2011 11:02, Török Edwin wrote:
On 10/14/2011 11:49 AM, Simon Friedberger wrote:
It seems that this error can be caused by different problems like a wrong inode
number when mounting CIFS or very large files. (Suggested by some websites and
old mailing list entries.)
What
Hi, Al!
On 14.10.2011 11:01, Al Varnell wrote:
On 10/14/11 1:49 AM, "Simon Friedberger" wrote:
3. How do I find out what the current maximum file size for scanning is?
The man page says the default is 25 MB but it is not set in /etc/clamav/
anywhere and I have scanned files larger than that.
On 10/14/2011 11:49 AM, Simon Friedberger wrote:
> Hello everybody,
>
> I'm getting the following error trying to scan a file:
>
> WARNING: myfilename: Can't access file
> myfilename: Value too large for defined data type
This probably comes from the stat() system call.
It can happen if you use
On 10/14/11 1:49 AM, "Simon Friedberger" wrote:
> 3. How do I find out what the current maximum file size for scanning is?
> The man page says the default is 25 MB but it is not set in /etc/clamav/
> anywhere and I have scanned files larger than that.
>
It's in clamd.conf, but if you run clamcon
Hello everybody,
I'm getting the following error trying to scan a file:
WARNING: myfilename: Can't access file
myfilename: Value too large for defined data type
It seems that this error can be caused by different problems like a
wrong inode number when mounting CIFS or very large files. (Sugge
12 matches
Mail list logo
