From: nizamhaider786@gmail.com (Nizam Haider)
To: kernelnewbies@lists.kernelnewbies.org
Subject: catch exit status of daemon
Date: Tue, 6 Jan 2015 19:27:12 +0000 (UTC) [thread overview]
Message-ID: <loom.20150106T202517-825@post.gmane.org> (raw)
In-Reply-To: CAJnfX5uizm-M7gyV3HkQ7qAQSeME-h5M=5VucU1So24mD0b=VQ@mail.gmail.com
Anuz Pratap Singh Tomar <chambilkethakur <at> gmail.com> writes:
>
>
>
> On Tue, Jan 6, 2015 at 3:22 PM, Yash Jain <yash2learn <at> gmail.com>
wrote:Hello All,I have one dumb question,
> I wanted to write a process which monitors the exit status of the daemon,
>
> The Main process would fork a service, which would internally fork a child
and , exit from the process. If main process wants to query the status of
the daemon, how it can be achived.
>
> For ex :
> Process A would call a syslog service, which would internally fork a
child, daemon it and exit, so if process A wants to wait for the syslog
process, is it possible.
>
>
> waitpid()
>
> signal()
WIFEXITED
WEXITSTATUS
>
>
>
> Thanks in advance
>
> Regards,
> Yash.
>
> _______________________________________________
> Kernelnewbies mailing listKernelnewbies <at>
kernelnewbies.orghttp://lists.kernelnewbies.org/mailman/listinfo/kernelnewbi
es
>
>
> -- Thank you Warm RegardsAnuz
>
>
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies <at> kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
next prev parent reply other threads:[~2015-01-06 19:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 15:22 catch exit status of daemon Yash Jain
2015-01-06 15:35 ` nick
2015-01-06 16:24 ` Valdis.Kletnieks at vt.edu
2015-01-06 16:46 ` Anuz Pratap Singh Tomar
2015-01-06 19:27 ` Nizam Haider [this message]
2015-01-07 8:05 ` Sudip Mukherjee
2015-01-07 9:10 ` Yash Jain
2015-01-07 22:58 ` Bernd Petrovitsch
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=loom.20150106T202517-825@post.gmane.org \
--to=nizamhaider786@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).