On a fresh install of nod32 antivirus 4.0.81.0 on Ubuntu 16.04 LTS, I first set Apparmor to "complain" mode for all profiles and then went through the instructions in the ESET KB article 3723 to create an eset.service file under /lib/systemd/system and start service using systemctl:
hxxp://support.eset.com/kb3723/?locale=en_US
However, now I'm seeing multiple version update messages from esets_gui, and syslog is filled with messages from esets_gui, esets_daemon, systemd, and others:
warning: Cannot read from socket: Resource temporarily unavailable
error: Cannot get setup from daemon: Daemon closed connection
(I also notice that /opt/eset/esets/lib/esets_mac is running in its own PID. Should that be?)
...along with multiple network freezes.
Other info from the NOD32 about dialog:
Module Version
Update 1062
AV and Antispyware scanner 1482
Virus sig db 13389
archive supp 1248
adv heuristics 1168
cleaner 1120
System info:
Linux 4.4.0-21-generic (64-bit) #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016
Intel® Core i7-5600U CPU
Any way to correct permissions, or maybe install a development build to correct the freeze issues?
