On Tue, 4 May 2021, Michael Wang wrote:
I do not disagree with you on the separate functionality of the scheduling
engine and scanning engine. The question is: does such an engine exist?
ClamWin has a scheduler
https://clamwin.com/content/view/71/1/
but, although based on ClamAV,
On 5/5/21 5:02 AM, Matus UHLAR - fantomas wrote:
Thus, it's not possible date ctime back without direct access to
filesystem (in which case your problem would be much bigger).
I agree with you given the standard operating procedure for many
decades. Though I do wonder if -> how the newer
On 04.05.21 14:19, Michael Wang wrote:
It seems that this should be a common question, but I did not find a
definite answer via Google search. I saw solutions to only scan files in
the last 60 days,
what solution? Something related to "find ... -mtime"?
but it is not difficult for a virus
On 5/4/21 2:54 PM, Michael Wang wrote:
I do not disagree with you on the separate functionality of the
scheduling engine and scanning engine. The question is: does such an
engine exist? I feel it is too much for each individual user to
implement such a scheduling engine. I am new to ClamAV,
Grant,
I do not disagree with you on the separate functionality of the scheduling
engine and scanning engine. The question is: does such an engine exist? I
feel it is too much for each individual user to implement such a scheduling
engine. I am new to ClamAV, does the question / solution ever pop
On 5/4/21 12:19 PM, Michael Wang wrote:
looks like this should be a functionality of the clamav itself.
What you are describing sounds like something independent of the ClamAV
/scanning/ engine. More specifically, it sounds like the responsibility
of a /scheduling/ engine.
My
On 5/4/21 1:41 PM, Benny Pedersen via clamav-users wrote:
fun part is that clamdscan needs root access, stupid
clamdscan does *NOT* /need/ root access.
clamdscan can scan files without root access perfectly fine.
What clamdscan /does/ /need/ is the ability to /access/ files to be
scanned.
On 2021-05-04 20:19, Michael Wang wrote:
It seems that this should be a common question, but I did not find a
definite answer via Google search. I saw solutions to only scan files
in the last 60 days, but it is not difficult for a virus file to
change date, isn't it? I can think of to maintain
It seems that this should be a common question, but I did not find a
definite answer via Google search. I saw solutions to only scan files in
the last 60 days, but it is not difficult for a virus file to change date,
isn't it? I can think of to maintain hash table with file name and its
checksum,
