Is there a way to do on-demand scanning without suffering the initializations delays from esets_scan?
I am using eset file security to scan files as needed, so I am using esets_scan. The issue I am having is that the initialization of esets_scan adds about 3 seconds to each scan.
Sample output of scan on a file:
>> date; /opt/eset/esets/sbin/esets_scan --clean-mode=none mySmallFile.txt; date
Fri Jul 7 19:40:40 UTC 2017
ESET Command-line scanner, version 4.5.6, (C) 1992-2016 ESET, spol. s r.o.
Using license: ************* (/etc/opt/eset/esets/license/esets_bda6db.lic)
Module loader, version 1069 (20161122), build 1112
Module perseus, version 1522.1 (20170621), build 1867
Module scanner, version 15710 (20170707), build 33982
Module archiver, version 1265 (20170623), build 1317
Module advheur, version 1177 (20170220), build 1144
Module cleaner, version 1135 (20170505), build 1173
Command line: --clean-mode=none file.txt
Scan started at: Fri 07 Jul 2017 07:40:43 PM UTC
Scan completed at: Fri 07 Jul 2017 07:40:43 PM UTC
Scan time: 0 sec (0:00:00)
Total: files - 1, objects 1
Infected: files - 0, objects 0
Cleaned: files - 0, objects 0
Fri Jul 7 19:40:43 UTC 2017
The output above shows that the actual scan itself took sub second and the initialization took 3 seconds. I am wondering if there is anyway I can avoid the initialization delay. Can I use esets_daemon for on-demand scanning (if so how?)? Is there a way to keep esets_scan pre-initialized? Are there options I can turn off in the configuration to shorten the initialization (since I only need scanning and no quarantining or any other features)? Any help would be appreciated. Thank you.