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
This option would change how non-converted attachments in all export formats, and database and other supporting files in a raw export (see #407) are copied: instead of clonefile(2), link(2) would be used to create hard links to the original files in the export. This would be useful when the user uses standard tooling (e.g. tar or rsync) to back up a directory hierarchy that contains both the original database and the export directory. Such tools recognize and handle hardlinks efficiently, but they don't detect when two files are clones of each other.
This discussion was converted from issue #405 on December 16, 2024 07:10.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This option would change how non-converted attachments in all export formats, and database and other supporting files in a raw export (see #407) are copied: instead of
clonefile(2)
,link(2)
would be used to create hard links to the original files in the export. This would be useful when the user uses standard tooling (e.g. tar or rsync) to back up a directory hierarchy that contains both the original database and the export directory. Such tools recognize and handle hardlinks efficiently, but they don't detect when two files are clones of each other.Beta Was this translation helpful? Give feedback.
All reactions