Report full path to driver socket (when we listen or fail to connect) #2771
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follows up from #2764 discussion.
Also reshuffle path-related char arrays to use a common
NUT_PATH_MAX
large enough for different platforms.Note that internally data server and driver programs generally deal with short base filenames of the sockets (e.g. in
ups->fn
values), assuming that theychdir
into the state path first. When people build custom NUT and mix some things from that build and others from packaging, they are at risk of using different state paths in different programs (e.g./var/state/ups
and(/var)/run/nut
) and this change should help discover and rectify this in troubleshooting, or rule it out as not the problem in a discussed case.Examples of output from
make check-NIT-sandbox-devel
:upsd
starting, not seeing UPSes:upsd
sees them:upsd
is running:upsd
with one driver not connected (invalid FD, killed off again):