Reconsider gethostname/UNISONLOCALNAME vs stored name in .unison #1026
Labels
discuss
way forward is unclear; needs discussion of approach to take and why
effort-high
issue is likely to require >20h of effort, perhaps much more
enhancement
issue is a request for a feature, and not a defect
impact-low
low importance
wontfix
maintainers choose not to work on this, but PR would still be considered
Currently unison uses the hostname archive names. This is problematic for hosts without stable names (e.g., those using dhcp without a local overrride to have the hostname as seen by gethostname(3) stable), and the UNISONLOCALNAME alternative appears too difficult in practice.
This ticket is to consider and perhaps implement alternatives, e.g.:
Also in scope for this issue is a tool to modify archive files to have a new name, given archives with an old name.
See also #1036 which is about keeping this sort of information bound to the replica instead of on the host that (currently) has the replica's filesystem.
The text was updated successfully, but these errors were encountered: