Re: AW: Questions to bash "read" builtin functionality

2012-12-19 Thread Greg Wooledge
On Wed, Dec 19, 2012 at 04:49:32PM -0500, Chet Ramey wrote: > I get the same results if I run the pipeline in an interactive shell. > This is pretty much what I expect. The whitespace and newlines will > disappear due to read's $IFS processing if they're first or last in > the string. Which is wh

Re: AW: Questions to bash "read" builtin functionality

2012-12-19 Thread Chet Ramey
On 12/17/12 3:34 AM, Fiedler Roman wrote: > From your description, I would expect > > --- HYPOTHETICAL-OUTPUT--- > # ./FragmentedSend.py | ./BashReadTest > Read status 142, value "" > Read status 142, value "Stat" << the partial read > FAILED READ: "us: OK" > Traceback (most recent call la

AW: AW: Questions to bash "read" builtin functionality

2012-12-17 Thread Fiedler Roman
> Von: Chet Ramey [mailto:chet.ra...@case.edu] > Gesendet: Montag, 17. Dezember 2012 15:10 > > On 12/17/12 3:34 AM, Fiedler Roman wrote: > > That is strange: If I understand correctly, following script combined with > > the > one from first mail should still fail, but with different error. But i

Re: AW: Questions to bash "read" builtin functionality

2012-12-17 Thread Chet Ramey
On 12/17/12 3:34 AM, Fiedler Roman wrote: > That is strange: If I understand correctly, following script combined with > the one from first mail should still fail, but with different error. But it > fails in a way similar to discarding partial input, not saving it. Could it > be, that Ubuntu-ba

AW: Questions to bash "read" builtin functionality

2012-12-17 Thread Fiedler Roman
> -Ursprüngliche Nachricht- > Von: Chet Ramey [mailto:chet.ra...@case.edu] > Gesendet: Samstag, 15. Dezember 2012 23:53 > > On 12/14/12 6:28 AM, Fiedler Roman wrote: > > Hello list, > > > > One of our bash-scrips failed with very low frequency but randomly. The > result was that exactly 1