Also, keep in mind the var location is also technically wrong, it goes to /usr/local/var/run/netdata but no freebsd port that i know of uses anything like this and instead uses /var, i.e. /var/db/netdata, /var/run, /var/cache/netdata, or /var/log/netdata. This isn't as much of a deal as the other issue but thought id mention it.

Also, keep in mind the var location is also technically wrong, it goes to /usr/local/var/run/netdata but no freebsd port that i know of uses anything like this and instead uses /var, i.e. /var/db/netdata, /var/run, /var/cache/netdata, or /var/log/netdata. This isn't as much of a deal as the other issue but thought id mention it.

That’s a very good point, and we will actually need to fix it eventually, though it will likely be more involved than just patching the build system.

That’s a very good point, and we will actually need to fix it eventually, though it will likely be more involved than just patching the build system.

If it helps, you can see how the port patches the installer to use appropriate directories here.

https://github.com/freebsd/freebsd-ports/tree/main/net-mgmt/netdata

More specifically this file

https://github.com/freebsd/freebsd-ports/blob/main/net-mgmt/netdata/files/patch-configure.ac

Quick update on this. It looks like --prefix=/foo actually works correctly, the issue seems to actually be in how the install/build code is invoking the config script (specifically, we’re explicitly adding /usr when we should not be). Fixing that should be dead simple, but actually testing the fix is not likely to be trivial as I suspect we have some code that blindly assumes the /usr component in the prefix generation.

The /var issue mentioned above is probably also not as complicated as I first thought, but is likely more complicated than the general prefix issue.

Hey @Ferroin , do we have any planes on fixing this one? Also, do we need a separate ticket for the /var issue?

The /var thing should be it’s own thing, but is likely to be fixed in a manner similar to this. There’s also the issue of us using /var/run in preference to /run on Linux (we should always be using /run on Linux, not /var/run) as well.

I’ve got the beginnings of a fix for the /usr issue, but it still needs a lot of work (a number of things are still not quite working correctly). I hope to have a PR ready for that some time before the end of the month, but it’s not been an especially high priority issue so far.