From: johan.adolfsson@axis.com
To: "john slee" <indigoid@higherplane.net>, <ebuddington@wesleyan.edu>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Dissociating process from bin's filesystem
Date: Thu, 25 Apr 2002 11:22:00 +0200 [thread overview]
Message-ID: <01c201c1ec3a$a78d5400$adb270d5@homeip.net> (raw)
In-Reply-To: <20020424224714.B19073@ma-northadams1b-46.bur.adelphia.net> <20020425085237.GE17717@higherplane.net>
Doesn't mlockall() do this?
man mlockall
/Johan
----- Original Message -----
From: "john slee" <indigoid@higherplane.net>
To: <ebuddington@wesleyan.edu>
Cc: <linux-kernel@vger.kernel.org>
Sent: den 25 april 2002 10:52
Subject: Re: Dissociating process from bin's filesystem
> On Wed, Apr 24, 2002 at 10:47:14PM -0400, Eric Buddington wrote:
> > Is there any way to dissociate a process from its on-disk binary? In
> > other words, I want to start 'foo_daemon', then unmount the filesystem
> > it started from. It seems to me this would be reasonably accomplished
> > by loading the binary completely into memory first ro eliminate the
> > dependence.
> >
> > Is this possible, or planned? Are there intractable problems with it
> > that I don't see?
>
> as i understand it this precludes you from using shared libs as they are
> mmap()'d on startup...
>
> other than that the running daemon will cause the fs to be
> un-umountable.
>
> j.
>
> --
> R N G G "Well, there it goes again... And we just sit
> I G G G here without opposable thumbs." -- gary larson
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2002-04-25 9:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-25 2:47 Eric Buddington
2002-04-25 3:42 ` James Cassidy
2002-04-25 8:52 ` john slee
2002-04-25 9:22 ` johan.adolfsson [this message]
2002-04-25 11:42 ` Padraig Brady
2002-04-27 19:03 ` Eric W. Biederman
2002-04-25 12:28 ` Rob Landley
2002-04-25 17:52 ` Chris Friesen
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='01c201c1ec3a$a78d5400$adb270d5@homeip.net' \
--to=johan.adolfsson@axis.com \
--cc=ebuddington@wesleyan.edu \
--cc=indigoid@higherplane.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®