util-vserver:InitStyles - Revision history

Glenn: + Category:Configuration

2011-10-21T21:17:29Z

+ Category:Configuration

KornAndras: /* Using runit */ rewording

2009-04-22T08:50:10Z

‎Using runit: rewording

90.149.13.151 at 10:24, 4 November 2008

2008-11-04T10:24:35Z

KornAndras: /* Using runit */ updates and pointer to new to-be-written page

2007-02-02T01:30:33Z

‎Using runit: updates and pointer to new to-be-written page

195.56.53.118: fix a sentence I broke during my last edit

2007-01-12T01:47:40Z

fix a sentence I broke during my last edit

195.56.53.118: Added "using runit"

2007-01-12T01:39:34Z

Added "using runit"

75.36.147.248: /* Configuration */

2006-12-14T01:17:27Z

‎Configuration

75.36.147.248: /* Configuration */

2006-12-14T01:16:49Z

‎Configuration

75.36.147.248 at 01:15, 14 December 2006

2006-12-14T01:15:04Z

75.36.147.248: /* Configuration */

2006-12-14T01:12:22Z

‎Configuration

← Older revision		Revision as of 21:17, 21 October 2011
Line 77:		Line 77:

	--[[User:KornAndras\|Guy-]] 02:30, 2 February 2007 (CET)		--[[User:KornAndras\|Guy-]] 02:30, 2 February 2007 (CET)
		+
		+	[[Category:Configuration]]

@@ Line 34: / Line 34: @@
 * Set initstyle to plain; this allows you to launch your own <tt>runit</tt> inside the vserver.
 * Set initstyle to <tt>sysv</tt>, but <tt>cmd.start</tt> to "<tt>/etc/runit/2</tt>" and <tt>cmd.stop</tt> to "<tt>/etc/runit/3</tt>".
-* Use a persistent context for the guest, and just run the services inside it, not runit itself. This is discussed in [[Running runit-supervised services inside a vserver]].
+** Advantage: you can run a vserver supervised by <tt>runit</tt> running on the host.
-−
-I haven't tried the first way; the second way has the advantage that you can run a vserver under <tt>runit</tt> running on the host.
 For this to work, you must customize <tt>/etc/runit/2</tt> in the vserver as follows:
@@ Line 74: / Line 74: @@
 ** You may want to add something to this effect to the <tt>finish</tt> script of the vserver service, but it may not be a good idea. Be sure you know what you are doing, as always.
-Still, this may not be the best way to integrate <tt>runit</tt> with vserver. I now believe the best way is [[running runit-supervised services inside a vserver]] without imitating anything like init in the guest.
+Still, this may not be the best way to integrate <tt>runit</tt> with vserver. [[Running runit-supervised services inside a vserver]] may be better if you only run a specific service in a guest and it seems wasteful to keep extra processes around. Using the plain initstyle and starting runit-init in each guest is best if you want to make your guests behave like a physical system. It's also the most hassle-free approach.
 --[[User:KornAndras|Guy-]] 02:30, 2 February 2007 (CET)

@@ Line 12: / Line 12: @@
 ** The vserver sees a fake init with PID 1 that has the same properties as the real init on the host.
 ** You must use "reboot -f" or "halt -f" to restart or shut down from within the guest.
 * gentoo
 ** Like sysv but works on Gentoo-based guests.

@@ Line 30: / Line 30: @@
 === Using runit ===
-[http://smarden.org/runit/ runit] is an init replacement that provides service monitoring. There currently are at least two ways to use it with vserver:
+[http://smarden.org/runit/ runit] is an init replacement that provides service monitoring. There currently are at least three ways to use it with vserver:
 * Set initstyle to plain; this allows you to launch your own <tt>runit</tt> inside the vserver.
 * Set initstyle to <tt>sysv</tt>, but <tt>cmd.start</tt> to "<tt>/etc/runit/2</tt>" and <tt>cmd.stop</tt> to "<tt>/etc/runit/3</tt>".
 I haven't tried the first way; the second way has the advantage that you can run a vserver under <tt>runit</tt> running on the host.
@@ Line 67: / Line 68: @@
 * If <tt>runsvdir</tt> terminates, all services running inside the vserver are stopped.
 * <tt>vserver stop</tt> works as expected.
 * You can control the vserver using <tt>sv</tt> like any other service, provided all processes running inside it are managed by <tt>runit</tt>.
 ** If there are processes left inside after all the services exited, <tt>runit</tt> running on the host won't be able to restart the vserver until those stray processes are killed somehow.
 ** You may want to add something to this effect to the <tt>finish</tt> script of the vserver service, but it may not be a good idea. Be sure you know what you are doing, as always.
-Still, this may not be the best way to integrate <tt>runit</tt> with vserver.
+Still, this may not be the best way to integrate <tt>runit</tt> with vserver. I now believe the best way is [[running runit-supervised services inside a vserver]] without imitating anything like init in the guest.

@@ Line 10: / Line 10: @@
 ** You can watch the startup process.
 ** Slightly lighter weight since no additional init process is needed.
-** The vserver sees a fake init with process 1 that has the same properties as the real init on the host.
+** The vserver sees a fake init with PID 1 that has the same properties as the real init on the host.
 ** You must use "reboot -f" or "halt -f" to restart or shut down from within the guest.
 * gentoo

@@ Line 2: / Line 2: @@
 * plain
-** Launches a unique init process for the guest.
+** Launches a unique init process for the guest that appears to run as PID 1.
 ** Guest's init process executes the rc scripts.
 ** Therefore, you cannot watch the startup process.
@@ Line 8: / Line 8: @@
 * sysv (default)
 ** Executes the runlevel scripts directly.
-** You can you can watch the startup process.
+** You can watch the startup process.
 ** Slightly lighter weight since no additional init process is needed.
-** A fake init process is shown in the guest.
+** The vserver sees a fake init with process 1 that has the same properties as the real init on the host.
 ** You must use "reboot -f" or "halt -f" to restart or shut down from within the guest.
 * gentoo
@@ Line 27: / Line 27: @@
 If the file doesn't exist, sysv will be used.  If the word isn't recognized, the guest will not be started and an error will be printed.

← Older revision		Revision as of 01:17, 14 December 2006
Line 26:		Line 26:
	/etc/vservers/<NAME>/apps/init/style		/etc/vservers/<NAME>/apps/init/style

−	If the file doesn't exist, sysv will be used. If the word isn't recognized, the ~~vserver~~ will not be started and an error will be printed.	+	If the file doesn't exist, sysv will be used. If the word isn't recognized, the guest will not be started and an error will be printed.

← Older revision		Revision as of 01:16, 14 December 2006
Line 26:		Line 26:
	/etc/vservers/<NAME>/apps/init/style		/etc/vservers/<NAME>/apps/init/style

−	If the file doesn't exist or the word isn't recognized, ~~sysv~~ will be ~~used~~.	+	If the file doesn't exist, sysv will be used. If the word isn't recognized, the vserver will not be started and an error will be printed.

@@ Line 22: / Line 22: @@
 === Configuration ===
-The init style should go in a file containing the init style as a single word.
+The init style should go in a file containing a single word: sysv, plain, etc.
    /etc/vservers/<NAME>/apps/init/style
 If the file doesn't exist or the word isn't recognized, sysv will be used.