linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Progga <abulfazl@juniv.edu>
To: Glynn Clements <glynn.clements@virgin.net>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Capturing output of a process.
Date: Fri, 19 Dec 2003 11:05:02 +0600	[thread overview]
Message-ID: <20031219110502.B340@Imrashi.net.bd> (raw)
In-Reply-To: <16354.21736.871304.763744@cerise.nosuchdomain.co.uk>; from glynn.clements@virgin.net on Fri, Dec 19, 2003 at 01:31:20AM +0000

On Fri, Dec 19, 2003 at 01:31:20AM +0000, Glynn Clements wrote:
 
> Most practical solutions involve allocating a pseudo-tty *before*
> starting the process whose output is to be logged.

 If I want to write something LIKE an SSL server, should I follow this same
technique to capture the output of a child process ?


 Khoda Hafez 
 Progga


  reply	other threads:[~2003-12-19  5:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-18 20:36 Capturing output of a process Ramanan, Venkat (MED)
2003-12-19  1:31 ` Glynn Clements
2003-12-19  5:05   ` Progga [this message]
2003-12-19  8:59     ` Glynn Clements
  -- strict thread matches above, loose matches on Subject: below --
2003-12-22 23:24 Ramanan, Venkat (MED)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20031219110502.B340@Imrashi.net.bd \
    --to=abulfazl@juniv.edu \
    --cc=glynn.clements@virgin.net \
    --cc=linux-c-programming@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).