Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reconsider gethostname/UNISONLOCALNAME vs stored name in .unison #1026

Open
gdt opened this issue Apr 26, 2024 · 0 comments
Open

Reconsider gethostname/UNISONLOCALNAME vs stored name in .unison #1026

gdt opened this issue Apr 26, 2024 · 0 comments
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

Comments

@gdt
Copy link
Collaborator

gdt commented Apr 26, 2024

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.:

  • generate a name from the hostname (with a uniquifier, UUID-ish) and store it in .unison, using that instead
  • as above, but stop pretending that it is a name

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.

@gdt gdt added enhancement issue is a request for a feature, and not a defect wontfix maintainers choose not to work on this, but PR would still be considered effort-high issue is likely to require >20h of effort, perhaps much more impact-low low importance discuss way forward is unclear; needs discussion of approach to take and why labels Apr 26, 2024
@gdt gdt changed the title Reconsider gethostname/UNISONLOCALNAME vs stored name in .unison or in replica itself Reconsider gethostname/UNISONLOCALNAME vs stored name in .unison May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

1 participant