You are not logged in.
When I run xz on a file, it sits there and grinds away for a while, then I eventually get file.xz. How does this process happen? Is it writing to a temporary file in the process? Also, is there a way to make an xz archive of a file without removing (or replacing) the original?
Offline
Also, is there a way to make an xz archive of a file without removing (or replacing) the original?
Taken from 'man xz', I didn't try it
-k, --keep
Don't delete the input files.
Ask, and it shall be given you.
Seek, and ye shall find.
Knock, and it shall be opened unto you.
Offline
When i use xz on a 1.2 GB test-file with redundant content, the corresponding archive file spawns instantly and then grows in size (regarding to watch wc) until the compression process is completed (about 2 min). Also, lsof|grep xz doesn't indicate, any temporarly files are involved.
So i suggest getting an earlier spawning (yet unfinished) archive might be more related to your desktop environment, its file alteration monitor (fam, gamin...) and file manager. Though, most file managers should have a manual refresh capability (e. g. ^r or f5).
Offline