Backup_agent fails to write logs if selinux is enabled

To solve the problem with SELinux, I suggest moving backup_agent to the “/usr/bin” folder. What do you think?

Sounds good to me (currently it’s in /usr/lib/foundationdb/backup_agent/backup_agent). Would be interested if this will cause anyone grief.

S

It should be noted that if CI foundationdb automatic update is configured, then after installing a new version of foundationdb, the path to backup_agent in foundationdb.conf will not be replaced and the log with the startup error will grow indefinitely.