From: "David Jackson" <david.jay.jackson@wcox.com>
To: Linux-Admin <linux-admin@vger.kernel.org>
Subject: FWD: [SATLUG] stdout redirection
Date: Fri, 28 Jun 2002 16:48:37 -0600 [thread overview]
Message-ID: <200206281648.AA1025376576@wcox.com> (raw)
This was posted to the San Antonio LUG group.
Any comments, suggestion to help this poor soul out.
David J
---------- Original Message ----------------------------------
From: mikewallace@softhome.net
Reply-To: satlug@satlug.org
Date: Wed, 26 Jun 2002 22:01:05 -0600
I've just written a program which is dumping various debugging information
to stdout. When I started the program running I forgot to add the pipe to
tee to also save the output in a file. So, armed with only the process id
of the program in question, is there a way that I can redirect stdout to
also go to a file without having to kill my program and restart it?
Basically, I want to attach a pipe to a program which is already executing.
Normally I'd just kill the process and restart it with the pipe to tee, but
I'm processing a huge chunk of data and I don't want to stop it in the
middle of it's execution.
Mike
_______________________________________________
Satlug mailing list
Satlug@satlug.org
http://alamo.satlug.org/mailman/listinfo/satlug
reply other threads:[~2002-06-28 22:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200206281648.AA1025376576@wcox.com \
--to=david.jay.jackson@wcox.com \
--cc=linux-admin@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).