mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Denis Vlasenko <vda@ilport.com.ua>
To: John Richard Moser <nigelenki@comcast.net>
Cc: linux-kernel@vger.kernel.org,
	ubuntu-devel <ubuntu-devel@lists.ubuntu.com>
Subject: Re: Keep initrd tasks running?
Date: Wed, 19 Oct 2005 14:07:26 +0300	[thread overview]
Message-ID: <200510191407.26665.vda@ilport.com.ua> (raw)
In-Reply-To: <4355494C.5090707@comcast.net>

On Tuesday 18 October 2005 22:13, John Richard Moser wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I have no idea who's the best to ask for this.
> 
> I want to start a task in an initrd and have it stay running after init
> is started.  Pretty much:
> 
> 
>  - kernel boot
>  - initrd loaded
>  - linuxrc executes
>  - /bin/mydaemon runs
>  - mount rootfs
>  - pivot_root
>  - exec /sbin/init (PID=1; linuxrc and sh is replaced)
>  - mydaemon keeps running, reparented under init, uninterrupted
> 
> 
> What's the feasibility of this without the system balking and vomiting
> chunks everywhere?  I'm pretty sure 'exec /sbin/init' from linuxrc
> (PID=1) will replace the process image of sh (linuxrc) with init,
> keeping PID=1; but I'm worried this may terminate children too.  Haven't
> tried.

It won't terminate children. Try it manually by booting with init=/bin/sh.
--
vda

      parent reply	other threads:[~2005-10-19 11:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-18 19:13 John Richard Moser
2005-10-18 19:29 ` Jeff Bailey
2005-10-18 19:38   ` John Richard Moser
2005-10-18 21:43     ` Jeff Bailey
2005-10-19  3:35   ` Phillip Susi
2005-10-19  4:22     ` John Richard Moser
2005-10-19 18:52       ` Phillip Susi
2005-10-23 20:40         ` Matt Zimmerman
2005-10-23 20:38       ` Matt Zimmerman
2005-10-18 19:37 ` linux-os (Dick Johnson)
2005-10-19 11:07 ` Denis Vlasenko [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=200510191407.26665.vda@ilport.com.ua \
    --to=vda@ilport.com.ua \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nigelenki@comcast.net \
    --cc=ubuntu-devel@lists.ubuntu.com \
    /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

Powered by JetHome