That sounds like things are on the right track. I appreciate the feedback.
For Debian, we want to always release with the latest clamav LTS and support
it through the lifecycle of a Debian release. We can, if needed move to a
newer release, particularly if libclamav binary compatibility is mai
Hi Scott,
> First, I see the planned EOL data on clamav.net is the same as then. Is the
assessment about extending the support period still ongoing?
We discussed it and agreed to a 1-year extension for 0.103 LTS (specifically)
but not all LTS versions. We have a blog draft in review at this mom
Hi Marc,
Well I got it to work except the logging (or at least it runs with no
errors) I tried the asterisk "*" and no, it doesn't work but adding a
space and \ gets it to be accepted. I do have yes to both --recursive
and --detect-pua set to yes. I just need to figure out the logging
thing and I'
as i explained before, please check all given paths.
it must start with "^/DIR/DIR/DIR/ [ ... so on]/"
please don't name folders or files only, always to whole path to dir/file!
i am not sure if the asterisk "*" work ...
by the way: you search with -recursive="yes" right?
then you don't need the "
Hi Marc & Andrew,
Okay now I'm really confused :-(
If I add what Andrew suggests it complains about "/usr/bin/clamscan:
unrecognized option" and points to the exclude thing. The $EXCLUDE=
getting removed fixes that and then gives this output:
$ ./clammy.sh
Loading:58s, ETA: 0s [===
--database="/etc/clamav/freshclam.conf" \ here you should have to path to your
.cvd, .dat, so on files
and not the dir to you conf file - clamscan did not support to read the
con.file while scanning
see clamscan --help
i think, this here will also not work, you create dynamically by date your l
