remote/exporter: support /usr/local/sbin/ser2net

[khilman]

Locally modified/compiled installs of ser2net could be in /usr/local, allow that as a fallback when not found in the other locations.

Signed-off-by: Kevin Hilman [email protected]

[Emantor]

Since this is just a fallback (which is already somewhat distribution specific), I think the correct way to solve this is to setup the correct PATH for the user/service calling the exporter and including /usr/local/bin/ there, since we try to resolve the PATH via which first.

[jluebbe]

@khilman would using $PATH work for you?

[khilman]

Using $PATH does work, but it's not great IMO. The problem with $PATH is that ser2net installs to /usr/local/sbin which is not typically in the path of a normal user. But I understand why you want to rely on $PATH so it's OK for me. It really only affects me until the ser2net features I'm using get pulled into distro versions of ser2net.

[Bastian-Krause]

It really only affects me until the ser2net features I'm using get pulled into distro versions of ser2net.

I'm assuming this happened in the meantime. So let's close this.