From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: [patch 4/5 salinfo-0.6] output
Date: Mon, 04 Oct 2004 06:25:58 +0000 [thread overview]
Message-ID: <11379.1096871158@kao2.melbourne.sgi.com> (raw)
output Stop stdout and stderr stamping on each other
Index: salinfo-0.6/salinfo_decode.c
=================================--- salinfo-0.6.orig/salinfo_decode.c Mon Oct 4 13:20:11 2004
+++ salinfo-0.6/salinfo_decode.c Mon Oct 4 13:22:07 2004
@@ -304,12 +304,12 @@ talk_to_sal (const char *type, const cha
type,
suffix);
fclose(stdout);
- if (!(stdout = fopen(filename, "w"))) {
+ if (!(stdout = fopen(filename, "a"))) {
perror(filename);
goto out;
}
fclose(stderr);
- if (!((stderr = fopen(filename, "w")))) {
+ if (!((stderr = fopen(filename, "a")))) {
perror(filename);
goto out;
}
reply other threads:[~2004-10-04 6:25 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=11379.1096871158@kao2.melbourne.sgi.com \
--to=kaos@sgi.com \
--cc=linux-ia64@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