All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Sturtevant <sturtx@gmail.com>
To: Pjotr Kourzanov <peter.kourzanov@xs4all.nl>,
	linux-kernel@vger.kernel.org
Subject: Re: fork/clone external to a process?
Date: Wed, 22 Dec 2004 08:50:21 -0500	[thread overview]
Message-ID: <7d9243330412220550602b2691@mail.gmail.com> (raw)
In-Reply-To: <41C936AF.7060707@xs4all.nl>

On Wed, 22 Dec 2004 09:56:15 +0100, Pjotr Kourzanov
<peter.kourzanov@xs4all.nl> wrote:

> 
>    What exactly are you referring to by "checkpoint" and "revert"? Do
> you mean temporarily stop and then resume?
> 

Checkpoint is a terrible name for what I want to do to the process. 
The only thing I mean is that I want one of the "forked" processes
either wait() ing for the other one to end or SIGSTOPed so I can wake
it up when the other ends.  The sleeping one will be in the state that
the other was in at the time of the fork.


>    Well, the kernel AFAIK makes deep copies of task structs only on
> behalf of a process (would be a security hole otherwise). I suppose you
> could change that, but I am afraid there will be a lot of resistance to
> it on LKML...
> 

I would never suggest anyone else do this to a kernel they care deeply about.

> >
> > My problem is that I want this to happen on demand rather than
> > whenever the substituted shared library call is invoked inside the
> > executable.
> >
> 
>    Do you really need /that/ flexibility? Just strace vmware and see
> what calls it does and when. Then just pick one that's in libc.so or
> another shared library. Don't forget to pass the call down to the
> original function;-)

I guess LD_PRELOAD could work.  It would be especially nice if I could
get inside a signal handler.

Thanks Pjotr

  parent reply	other threads:[~2004-12-22 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-21 15:49 fork/clone external to a process? Dan Sturtevant
2004-12-21 23:26 ` Pjotr Kourzanov
2004-12-22  0:36   ` Dan Sturtevant
     [not found]     ` <41C936AF.7060707@xs4all.nl>
2004-12-22 13:50       ` Dan Sturtevant [this message]
2004-12-25 22:26     ` Pavel Machek
2005-02-24  0:01       ` Dan Sturtevant

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=7d9243330412220550602b2691@mail.gmail.com \
    --to=sturtx@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.kourzanov@xs4all.nl \
    /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.