On 8/24/16 5:04 PM, Adam Danischewski wrote:
> Actually I misspoke before, there /is /this issue on Solaris 10. I didn't
> update the logic sufficiently to detect it at first. So it looks like this
> is could be a potentially more significant issue -- affecting enterprise
> user markets.
I sugges
On Wed, Aug 24, 2016 at 05:04:17PM -0400, Adam Danischewski wrote:
> be allowed, since I do not want things like a squirrely child process
> eating up parent pipe data in my while/read loops.
http://mywiki.wooledge.org/BashFAQ/089
Actually I misspoke before, there *is *this issue on Solaris 10. I didn't
update the logic sufficiently to detect it at first. So it looks like this
is could be a potentially more significant issue -- affecting enterprise
user markets.
I think the bottom line question is, should a child process be
On Wed, Aug 24, 2016 at 02:52:01PM -0400, Adam Danischewski wrote:
> When a parent script kicks off a child process, and the child process reads
> from fd0 I don't expect the child to be capable of manipulating the parents
> pipe data on fd0. An error potentially but not quietly eating up the
> par
Let's put aside the fs type for second and talk about what data should be
there and what should and shouldn't happen.
When a parent script kicks off a child process, and the child process reads
from fd0 I don't expect the child to be capable of manipulating the parents
pipe data on fd0. An error p
On 8/24/16 12:09 PM, Adam Danischewski wrote:
> I was expecting it to be the pts.
OK. That's just not how it works.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRUc...@case.eduhttp://cnswww
I was expecting it to be the pts.
On Tue, Aug 23, 2016 at 4:58 PM, Chet Ramey wrote:
> On 8/23/16 2:28 PM, Adam Danischewski wrote:
> > I'm not sure if this is a bug, or a feature but I had to debug some code
> as
> > a result so I'd like to bring it to your attention, and if you know of a
> > b
On 8/23/16 2:28 PM, Adam Danischewski wrote:
> I'm not sure if this is a bug, or a feature but I had to debug some code as
> a result so I'd like to bring it to your attention, and if you know of a
> better way to read from pipes please let me know.
Just so I'm not confused: you mean that you don
