Description of problem: frr uses /usr/lib/frr/ rather using /usr/libexec/frr/ or /usr/(s)bin/, thus executable daemon binaries are ending up in /usr/lib/frr/ actually. Version-Release number of selected component (if applicable): frr-7.3-4.fc33 How reproducible: See above. Actual results: Usage of /usr/lib/frr/ for daemon executables rather libraries. Expected results: Usage of /usr/libexec/frr/ for daemon executables (or /usr/(s)bin/).
Hi Robert, I was sort-of following the upstream's idea about this location. When frr was still quagga, my previous maintainer packaged it so that each daemon would have its own unit file and could be started via systemd. Since then, frr developers reverted all of this and created a new initscript that would start up all of the daemons at once. I tried to argue with them that this was not a good idea but it led nowhere. Since all of the frr's processes are started via frrinit.sh, I don't see a problem with it being located in /usr/lib/frr together with all the other scripts and binaries. As for the libexec vs. lib directories, I don't really see much of an effective difference here. Regards, Michal
I am closing this as WONTFIX. If you feel that this should be addressed, feel free to re-open this bug and we can discuss this.