| Summary: | hardlinked files could cause problems with git for network configuration files | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Dominic Hopf <dmaphy> |
| Component: | etckeeper | Assignee: | Thomas Moschny <thomas.moschny> |
| Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | el5 | CC: | thomas.moschny |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-07-02 11:50:44 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Dominic Hopf
2011-03-13 11:55:29 UTC
Hard linked network configuration files in /etc is quite normal for static network configs on RHEL or Fedora, but will vanish eventually when people use Network Manager only. Discussed a little bit with upstream, but it is not clear yet how to fix that issue. Git simply cannot handle hard links (and also breaks them when updating one of the linked files). That is not something etckeeper can easily simulate in general. For the case of the hard linked network config files though, one could come up with a special script that runs after /etc/etckeeper/pre-commit.d/30store-metadata and records them in /etc/.etckeeper, so they can be restored later. Patches welcome! Closing for now, unless sb comes up with a good idea how to deal with hardlinks in in Git in general. |