You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #25 we added support for persistent genid, but got the path wrong.
On Linux based systems we should honor the FHS:
"An application (or a group of inter-related applications) must use a subdirectory of /var/lib for its data.
There is one > required subdirectory, /var/lib/misc, which is intended for state files that don't need a subdirectory; ..."
On UNIX systems we should use /var/db.
Hence, _PATH_VARDB in /usr/include/paths.h really is the one to rely on here. Except some C-libraries on Linux still use /var/db, and the system is not guaranteed to have that path, or even a symlink to /var/lib/misc. So, we can either guess/probe on the system or make this a configure option, because some users don't even want to follow the FHS or a traditional hier(7).
The text was updated successfully, but these errors were encountered:
Follow-up to #37 in 5438ff3, which somehow failed to fix this issue
properly. To make matters worse, however, it turns out there are
several Linux systems out there still that has _PATH_VARDB set to
/var/db instead of the FHS standardized /var/lib/misc, so we have
to add a check for that too.
Signed-off-by: Joachim Wiberg <[email protected]>
In #25 we added support for persistent genid, but got the path wrong.
On Linux based systems we should honor the FHS:
On UNIX systems we should use
/var/db
.Hence,
_PATH_VARDB
in/usr/include/paths.h
really is the one to rely on here. Except some C-libraries on Linux still use/var/db
, and the system is not guaranteed to have that path, or even a symlink to/var/lib/misc
. So, we can either guess/probe on the system or make this a configure option, because some users don't even want to follow the FHS or a traditional hier(7).The text was updated successfully, but these errors were encountered: