Re^3: Detecting Timeout of piped data

Shouldn't the chomp between the read and the check remove the \n thereby making $inLine eq ''?

What I believe ( and certainly could be wrong ) is that the script is just sitting and waiting at $inLine = <>; without ever recieving anything, and so never gets to any of the code that follows except when there is input. I think what I am looking for is something like the <> but with a configurable timeout period.

Comment on Re^3: Detecting Timeout of piped data

Replies are listed 'Best First'.
Re^4: Detecting Timeout of piped data by Anonymous Monk on Aug 01, 2011 at 05:55 UTC
I looked before and I looked now and I don't see a chomp is the original code. It could be there but and I'm not seeing it but, yes, chomp would fix that problem. As for your analysis that the program is sitting in an idle loop, well, yes, that is the main problem, but I thought sierpinski had already said that.	[reply]
Re^5: Detecting Timeout of piped data by Anonymous Monk on Aug 01, 2011 at 05:57 UTC
Sorry for replying to myself but that's the price of being anon.... I didn't mean to sound harsh. You are right.	[reply]
Re^4: Detecting Timeout of piped data by Anonymous Monk on Aug 01, 2011 at 06:04 UTC
Wow, I'm really sorry, I shouldn't be posting when I'm drunk, I thought you were trying to help rather than the guy with the question. That said, check out what zentara had to say about alarm. Alternatives might be non-blocking reads and using select with a timeout. Again, sorry, I'll just go away and leave you in peace now ;^)	[reply]