We could detect that archive contents are coming from terminal input and
fail immediately (IIRC tar waits indefinitely ATM until it's input is cut
by ctrl+d or it is killed).
I meant something like the patch attached, could you please consider?
I tried to write testcase for this and I failed
Pavel Raiskup wrote:
We could detect that archive contents are coming from terminal input and
fail immediately (IIRC tar waits indefinitely ATM until it's input is cut
by ctrl+d or it is killed).
I think this may be a good idea. It is a common feature among the
compressors used by tar:
$
On 03/13/2014 01:21 AM, Pavel Raiskup wrote:
We could detect that archive contents are coming from terminal input and
fail immediately (IIRC tar waits indefinitely ATM until it's input is cut
by ctrl+d or it is killed).
I meant something like the patch attached, could you please consider?
I
On 03/13/2014 10:35 AM, Paul Eggert wrote:
On 03/13/2014 01:21 AM, Pavel Raiskup wrote:
We could detect that archive contents are coming from terminal input and
fail immediately (IIRC tar waits indefinitely ATM until it's input is
cut
by ctrl+d or it is killed).
I meant something like the
Hello,
I have an issue with tar, it seems tar manages to create archive of files
larger than 8GB how ever, the header becomes curropted and thus tar is unable
to extract the archive. I've Googled around and all solutions that were given
were not the ones I needed.
I wanted to know if this bug
On 03/12/2014 01:47 AM, d.b.e wrote:
I have an issue with tar, it seems tar manages to create archive of
files larger than 8GB how ever, the header becomes curropted and thus
tar is unable to extract the archive.
I cannot reproduce the bug with tar 1.27.1 (which I built for Fedora 20
Hello Dan,
I have an issue with tar, it seems tar manages to create archive of
files larger than 8GB how ever, the header becomes curropted and thus
tar is unable to extract the archive.
what format are you using?
The 'pax' format (e.g.) is able to store files larger than 8GB and it
works
On Wednesday, March 12, 2014 11:00:14 Paul Eggert wrote:
I cannot reproduce the bug with tar 1.27.1 (which I built for Fedora 20
x86-64). Can you please give a recipe? Here's how I tried:
Dan replied to me off-list accidentally. The problem was just misuse of
tar's options (tar -x
Pavel Raiskup wrote:
We should probably detect terminal archive input/output and fail
appropriately?
tar always does something like that. Sorry, I don't understand the
failure scenario here.
On Wednesday, March 12, 2014 16:08:58 Paul Eggert wrote:
Pavel Raiskup wrote:
We should probably detect terminal archive input/output and fail
appropriately?
tar always does something like that. Sorry, I don't understand the
failure scenario here.
We could detect that archive contents
10 matches
Mail list logo
