Re: /usr/bin/tar creates invalid lib file

From: Tim Kientzle <tim_at_kientzle.com>
Date: Sun, 25 Mar 2012 16:32:53 -0700

On Mar 25, 2012, at 2:43 PM, Gleb Kurtsou wrote:

> I experience a related issue. lseek(SEEK_HOLE) error checks are too
> strict. Files are not added to archive if lseek(SEEK_HOLE) fails.
> Ignoring lseek(SEEK_HOLE) at least in ENOTTY case would be preferable.

Just noticed that lseek(1) doesn't document ENOTTY as
a valid response code.

Should it?

Tim

Received on Sun Mar 25 2012 - 21:32:54 UTC

This message: [ Message body ]
Next message: Konstantin Belousov: "Re: /usr/bin/tar creates invalid lib file"
Previous message: Tim Kientzle: "Re: /usr/bin/tar creates invalid lib file"
In reply to: Gleb Kurtsou: "Re: /usr/bin/tar creates invalid lib file"
Next in thread: Konstantin Belousov: "Re: /usr/bin/tar creates invalid lib file"
Reply: Konstantin Belousov: "Re: /usr/bin/tar creates invalid lib file"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:25 UTC