kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: krinkin.m.u@gmail.com (Mike Krinkin)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Attach my own pid
Date: Tue, 22 Mar 2016 11:08:52 +0300	[thread overview]
Message-ID: <20160322080852.GA3136@kmu-ThinkPad-X230> (raw)
In-Reply-To: <CAKfJ7K+jKbDiNOe4JqBdfS+2JL+SVjTWeTxsvp2udD0ET8Ot2w@mail.gmail.com>

On Sun, Mar 20, 2016 at 02:07:29AM -0700, Nitin Varyani wrote:
> Hi,
>      The linux kernel attaches a pid to newly forked process. I want to
> create a facility by which a process has the option of attaching a new pid
> to its child which is not in the pid space.
>       Any suggestions of how this can be achieved?
> Nitin

Don't know what you are trying to accomplish, but have a look at this:

https://criu.org/Pid_restore

> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      parent reply	other threads:[~2016-03-22  8:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-20  9:07 Attach my own pid Nitin Varyani
2016-03-20 18:33 ` Valdis.Kletnieks at vt.edu
2016-03-21  5:03   ` Nitin Varyani
2016-03-21  6:53     ` Valdis.Kletnieks at vt.edu
2016-03-21 10:31       ` Nitin Varyani
2016-03-21 10:33         ` Nitin Varyani
2016-03-21 10:47           ` Nitin Varyani
     [not found]           ` <CA+aCy1G351o4w-SFKaic_o-2MDOqNN+dTNfJEQteQof8CvopCQ@mail.gmail.com>
2016-03-21 11:04             ` Nitin Varyani
2016-03-22  3:22               ` Pranay Srivastava
2016-03-22  5:26         ` Valdis.Kletnieks at vt.edu
2016-03-22 10:25           ` Bernd Petrovitsch
2016-03-27 11:27             ` Nitin Varyani
2016-03-27 11:31               ` Nitin Varyani
2016-03-22  8:08 ` Mike Krinkin [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=20160322080852.GA3136@kmu-ThinkPad-X230 \
    --to=krinkin.m.u@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).