From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: "MATSUDA, Daiki" <matsudadik@intellilink.co.jp>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 2/8] qemu-ga: move channel/transport functionalit
Date: Fri, 03 Feb 2012 11:07:38 -0600 [thread overview]
Message-ID: <4F2C145A.3050002@linux.vnet.ibm.com> (raw)
In-Reply-To: <4F2B61CE.7040701@intellilink.co.jp>
On 02/02/2012 10:25 PM, MATSUDA, Daiki wrote:
> 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
>
Hi Matsuda,
Thank you for testing!
In the become_daemon() function, the parent exits immediately after the
fork(), so only the child has the opportunity to write to the pid file.
It calls getpid() to get the pid to write, which should be it's own
lwpid. So I'm not seeing where there's an opportunity for the parent pid
to be written.
Can you confirm? It seems to behave as expected for me:
[root@vm ~]# /home/mdroth/w/qemu-build/qemu-ga -d
** (process:7441): DEBUG: starting daemon
[root@vm ~]# ps aux | grep qemu-ga
root 7442 0.0 0.0 13792 348 ? Ss 10:56 0:00
/home/mdroth/w/qemu-build/qemu-ga -d
root 7471 0.0 0.1 109108 816 pts/2 R+ 11:00 0:00 grep
--color=auto qemu-ga
[root@vm ~]# cat /var/run/qemu-ga.pid
7442
next prev parent reply other threads:[~2012-02-03 17:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 4:25 [Qemu-devel] [PATCH v2 2/8] qemu-ga: move channel/transport functionalit MATSUDA, Daiki
2012-02-03 17:07 ` Michael Roth [this message]
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=4F2C145A.3050002@linux.vnet.ibm.com \
--to=mdroth@linux.vnet.ibm.com \
--cc=matsudadik@intellilink.co.jp \
--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).