Jump to content


  • Content Count

  • Joined

  • Last visited

Profile Information

  • Location
  1. Exclusions would work for us, but they don't appear to be working? I added "/root/*" to the exclusion list. Checked /etc/opt/eset/esets/esets.cfg and found "av_exclude = "/root/*::". Seems correct going off the main pages for esets.cfg. Restarted the esets_daemon (Not sure if necessary). Ran: /opt/eset/esets/sbin/esets_scan /root Summary of scan: Total: files - 1399, objects 4694 Thought maybe it wasn't really scanning but counting. So performed an strace and it's indeed opening files to scan them.
  2. I'll check it out. Is there currently any workaround that you know of to limit the scans to local mounts on a Linux server? Even if it's editing a cfg file on each server, that's fine. We just can't have multiple servers connecting to NFS/Samba shares and scanning them at the same time. Thanks
  3. I'm setting up client tasks within Security Management Center to handle scans of different groups of systems that we have. I can set up the scheduled tasks fine, but when using pre-defined targets such as ${DriveFixed} nothing is scanned, it works fine when I specify by mount point. These are mostly Linux servers if it matters. I am assuming the syntax is the same as ERA: https://help.eset.com/era_admin/65/en-US/client_tasks_on_demand_scan.html Any insight would be appreciated. Thanks!