[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Help-bash] catching read error conditions
From: |
Dan Douglas |
Subject: |
Re: [Help-bash] catching read error conditions |
Date: |
Mon, 28 Jan 2013 19:05:01 -0600 |
User-agent: |
KMail/4.8.3 (Linux/3.4.6-pf+; KDE/4.8.3; x86_64; ; ) |
On Monday, January 28, 2013 06:51:52 PM you wrote:
> /* `read -t 0 var' tests whether input is available with select/FIONREAD,
> ...
>
> Don't know whether that's worth testing or improves reliability in your
> case.
Oh this is actually documented, nevermind, I missed it clearly earlier. I just
noticed that note digging for how Bash did the timeout.
--
Dan Douglas
- [Help-bash] catching read error conditions, Mart Frauenlob, 2013/01/26
- Re: [Help-bash] catching read error conditions, Greg Wooledge, 2013/01/28
- Re: [Help-bash] catching read error conditions, Chet Ramey, 2013/01/28
- Re: [Help-bash] catching read error conditions, Mart Frauenlob, 2013/01/28
- Re: [Help-bash] catching read error conditions, Chet Ramey, 2013/01/28
- Re: [Help-bash] catching read error conditions, Mart Frauenlob, 2013/01/28
- Re: [Help-bash] catching read error conditions, Chet Ramey, 2013/01/28
- Re: [Help-bash] catching read error conditions, Mart Frauenlob, 2013/01/28
- Re: [Help-bash] catching read error conditions, Dan Douglas, 2013/01/28
- Re: [Help-bash] catching read error conditions,
Dan Douglas <=
- Re: [Help-bash] catching read error conditions, Mart Frauenlob, 2013/01/29
- Re: [Help-bash] catching read error conditions, Steven W. Orr, 2013/01/28
Re: [Help-bash] catching read error conditions, Mart Frauenlob, 2013/01/28