From: Rusty Russell <rusty@rustcorp.com.au>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Jerone Young <jyoung5@us.ibm.com>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] tools/xenstore/xenstore_core.c
Date: Fri, 12 Aug 2005 13:09:18 +1000 [thread overview]
Message-ID: <1123816158.28457.10.camel@localhost.localdomain> (raw)
In-Reply-To: <a4073d5e2f0063145b10c371a6c8fc0a@cl.cam.ac.uk>
On Thu, 2005-08-11 at 23:02 +0100, Keir Fraser wrote:
> This one's a bug, but I don't think that's the right fix. Rusty?
Yeah, we used to close stdout earlier, so this used a temporary dup'ed
fd. It's now much simpler: nice spotting Jerone.
Rusty.
# HG changeset patch
# User Rusty Russell <rusty@rustcorp.com.au>
# Node ID 1f532dacdc4870c235d57c55b2f6051b9ee40419
# Parent 822566f5cfddce3b641b5a1a119dfd592ec69158
Fix --output-pid (broken when we fixed --pid-file).
Thanks to Jerone Young for spotting this.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
diff -r 822566f5cfdd -r 1f532dacdc48 tools/xenstore/xenstored_core.c
--- a/tools/xenstore/xenstored_core.c Thu Aug 11 22:18:27 2005
+++ b/tools/xenstore/xenstored_core.c Fri Aug 12 03:08:56 2005
@@ -1587,7 +1587,7 @@
int main(int argc, char *argv[])
{
- int opt, *sock, *ro_sock, event_fd, max, tmpout;
+ int opt, *sock, *ro_sock, event_fd, max;
struct sockaddr_un addr;
fd_set inset, outset;
bool dofork = true;
@@ -1673,9 +1673,8 @@
restore_existing_connections();
if (outputpid) {
- char buffer[20];
- sprintf(buffer, "%i\n", getpid());
- write(tmpout, buffer, strlen(buffer));
+ printf("%i\n", getpid());
+ fflush(stdout);
}
/* close stdin/stdout now we're ready to accept connections */
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
prev parent reply other threads:[~2005-08-12 3:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 21:15 [PATCH] tools/xenstore/xenstore_core.c Jerone Young
2005-08-11 22:02 ` Keir Fraser
2005-08-12 3:09 ` Rusty Russell [this message]
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=1123816158.28457.10.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=jyoung5@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.