Bug #2588

xz(1) broken on DragonFly 3.5

Added by ftigeot about 1 year ago. Updated 8 months ago.

Status:ClosedStart date:09/26/2013
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

Besides burning CPU, the xz command has no visible effect on DragonFly 3.5.

In contrast, xz file.tar immediately starts creating a second (hidden) file on DragonFly 3.4.

History

#1 Updated by swildner about 1 year ago

On Thu, 26 Sep 2013 16:12:37 +0200,
wrote:

> Besides burning CPU, the xz command has no visible effect on DragonFly
> 3.5.

Surely not as generally as you put it.

An 1.25GB file took ~17 minutes to xz here on a rather old box.

zoot# ls -l hyperv.tar
-rw-r--r-- 1 root wheel 1347233792 Aug 12 13:51 hyperv.tar
zoot# time xz hyperv.tar
1038.500u 15.003s 17:39.77 99.4% 29+73k 84+12712io 2pf+0w
zoot# ls -l hyperv.tar.xz
-rw-r--r-- 1 root wheel 843640560 Aug 12 13:51 hyperv.tar.xz

Sascha

#2 Updated by swildner 8 months ago

  • Status changed from New to Closed

Closing this for now. It seems to not have been a general issue. Please reopen if there are any issues still.

Also available in: Atom PDF