On 08/17/2014 04:12 PM, Chet Ramey wrote:
> Bash uses lseek to the current file position to check this. If the lseek
> returns -1/EPIPE, bash assumes the fd is not seekable. If it returns 0,
> bash assumes that it can move around freely. Since bash is trying to seek
> backwards in the file, stdi
On 8/17/14, 1:47 AM, Linda Walsh wrote:
> ?? Could this be a cygwin bug? It's hard to see why cygwin
> would start using lseek calls when running bash unless bash called
> them... but then tha's not to say something else entirely may be going on as
> this is running on Windows... ;-/
The origina
?? Could this be a cygwin bug? It's hard to see why cygwin
would start using lseek calls when running bash unless bash called
them... but then tha's not to say something else entirely may be going on as
this is running on Windows... ;-/
forwarded as I thought it might be of interest here...
--
