Jump to content

Ben R

Members
  • Content Count

    2
  • Joined

  • Last visited

Profile Information

  • Location
    Australia
  1. Hi Tech Lounge, oh that was so easy that part... not! Search Replaced modified the EraAgentInstaller.sh file for all the mktemp bits and set the variable -tmpdir e.g: local_cert_path="$(mktemp -q -u --tmpdir=/cabs/eset)" Then (so it would start), I modified the /etc/systemd/system/eraagent.service systemd launcher to use the Environment variable as follows: Environment="MODMAPDIR=/var/opt/eset/RemoteAdministrator/Agent/" Environment="HOME=/var/opt/eset/RemoteAdministrator/Agent/" I think I did something else too.. but I can't remember. I have managed
  2. Hi Guys, Long term browser, first time poster here. We run a whole lot of Centos Linux boxes, majority on Centos 7. As all our boxes are providing internet based service we're keen to keep the noexec attribute on our /tmp folders which as many of you Linux buffs would know causes pain with the ESET products. I've got the ERA Agent installed finally (after adding custom environment variables to the systemd service file) and tried to deploy File Security but am still getting reference to /tmp permission issues - Observe: tail: /var/log/eset/RemoteAdministrator/Agent
×
×
  • Create New...