To prevent uncomfortable surprises, xz has a built-in memory usage limiter, which is disabled by default. xz files that require several gigabytes of memory to decompress.Įspecially users of older systems may find the possibility of very large memory usage annoying. For example, decompressing a file created with xz -9 currently requires 65 MiB of memory. Typically the decompressor needs 5% to 20% of the amount of memory that the compressor needed when creating the file. The settings used when compressing a file determine the memory requirements of the decompressor. The memory usage of xz varies from a few hundred kilobytes to several gigabytes depending on the compression settings. This has only limited use since when standard error is a terminal, using -verbose displays an automatically updating progress indicator. Sending SIGINFO or SIGUSR1 signals to the xz process makes it print progress information to standard error. The source file is never removed if the output is written to standard output. Once the target file is successfully closed, the source file is removed unless -keep was specified. xz doesn't support copying other metadata like access control lists or extended attributes yet. If copying the group fails, the permissions are modified so that the target file doesn't become accessible to users who didn't have permission to access the source file. tlz).Īfter successfully compressing or decompressing the file, xz copies the owner, group, permissions, access time, and modification time from the source file to the target file.
0 Comments
Leave a Reply. |