[shell-discuss] Problem capturing stdout from fork'd process

2008-09-11 Thread Glenn Fowler
On Thu, 11 Sep 2008 12:55:30 -0700 Steve Nash wrote: > Sorry, here's the URL: > http://bugs.opensolaris.org/view_bug.do?bug_id=6745015 > it looks like it doesn't have the latest comments yet, but there are > some more details. > > does the daemon do fork/fork to get into the background? > Th

[shell-discuss] Problem capturing stdout from fork'd process

2008-09-11 Thread James Carlson
Glenn Fowler writes: > > is there a 'CR 6745015' to url map? http://bugs.opensolaris.org/view_bug.do?bug_id=6745015 -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fa

[shell-discuss] Problem capturing stdout from fork'd process

2008-09-11 Thread Glenn Fowler
is there a 'CR 6745015' to url map? does the daemon do fork/fork to get into the background? On Thu, 11 Sep 2008 12:38:52 -0700 Steve Nash wrote: > We ran into a problem on OpenSolaris with a script we use in our product > that uses /bin/sh. See CR 6745015 for the gory details, but the gist is

[shell-discuss] Problem capturing stdout from fork'd process

2008-09-11 Thread Steve Nash
Glenn Fowler wrote: > On Thu, 11 Sep 2008 12:55:30 -0700 Steve Nash wrote: >> Sorry, here's the URL: > >> http://bugs.opensolaris.org/view_bug.do?bug_id=6745015 > >> it looks like it doesn't have the latest comments yet, but there are >> some more details. > >> > does the daemon do fork/fork t

[shell-discuss] Problem capturing stdout from fork'd process

2008-09-11 Thread Steve Nash
Sorry, here's the URL: http://bugs.opensolaris.org/view_bug.do?bug_id=6745015 it looks like it doesn't have the latest comments yet, but there are some more details. > does the daemon do fork/fork to get into the background? There is just one fork. Steve Glenn Fowler wrote: > is there a '

[shell-discuss] Problem capturing stdout from fork'd process

2008-09-11 Thread Steve Nash
We ran into a problem on OpenSolaris with a script we use in our product that uses /bin/sh. See CR 6745015 for the gory details, but the gist is that our script uses: VARIABLE=`command substitution` and the `command substitution` starts a daemon process that prints the message we want to capt