From: "MATSUDA, Daiki" <matsudadik@intellilink.co.jp>
To: qemu-devel@nongnu.org, Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v2 2/8] qemu-ga: move channel/transport functionalit
Date: Fri, 03 Feb 2012 13:25:50 +0900 [thread overview]
Message-ID: <4F2B61CE.7040701@intellilink.co.jp> (raw)
Hi, Michael!
Thank you for your working.
And I have a question the process id written in pid file.
If qemu-ga is ran as daemon, the parent process id not child is written
in pid file. So, id gotten by 'ps' command is different. Is it correct
work? Many other daemon writes child process id.
Regards
MATSUDA Daiki
next reply other threads:[~2012-02-03 4:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 4:25 MATSUDA, Daiki [this message]
2012-02-03 17:07 ` [Qemu-devel] [PATCH v2 2/8] qemu-ga: move channel/transport functionalit Michael Roth
2012-02-10 2:26 ` MATSUDA, Daiki
2012-02-10 4:51 ` Michael Roth
2012-02-13 2:14 ` MATSUDA, Daiki
2012-02-13 21:37 ` Michael Roth
2012-02-14 1:59 ` MATSUDA, Daiki
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=4F2B61CE.7040701@intellilink.co.jp \
--to=matsudadik@intellilink.co.jp \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.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).