<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="http://dev1galaxy.org/extern.php?action=feed&amp;tid=4952&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / [SOLVED] Runit - sym-linking sv]]></title>
		<link>http://dev1galaxy.org/viewtopic.php?id=4952</link>
		<description><![CDATA[The most recent posts in [SOLVED] Runit - sym-linking sv.]]></description>
		<lastBuildDate>Wed, 23 Mar 2022 14:57:55 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: [SOLVED] Runit - sym-linking sv]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=35355#p35355</link>
			<description><![CDATA[<p>I have now got a run script working for Xen and will report separately.</p><p>The use of sym-linking sv, taken from the link xinomilo gave above, seems to be as follows, assuming you have the foo daemon (food) working via a Runit run file :-</p><div class="codebox"><pre><code>/etc/init.d/food stop
dpkg-divert --add /etc/init.d/food
mv /etc/init.d/food /etc/init.d/food.distrib &amp;&amp;
   ln -s /usr/bin/sv /etc/init.d/food
update-service --add /etc/sv/food</code></pre></div><p>you can then use either of the following styles of command :-</p><div class="codebox"><pre><code>sv status food</code></pre></div><p>or</p><div class="codebox"><pre><code>/etc/init.d/food status</code></pre></div><p>to access the foo service under Runit.</p><p>Geoff</p>]]></description>
			<author><![CDATA[dummy@example.com (Geoff 42)]]></author>
			<pubDate>Wed, 23 Mar 2022 14:57:55 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=35355#p35355</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Runit - sym-linking sv]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=35345#p35345</link>
			<description><![CDATA[<p>OK, thank you for that link. I think it is saying that Runit still requires a proper Runit setup for the service, but you can have it controlled as though it were a SysV init script.</p><p>I have not found a Runit setup for xen and have been trying to convert the SysV init script into a Runit run script. To stop it looping I have added</p><div class="codebox"><pre><code>sv once xen</code></pre></div><p>which has the desired effect of stopping the looping when it is not booted on Xen, but more testing is required ;-)</p><p>Geoff</p>]]></description>
			<author><![CDATA[dummy@example.com (Geoff 42)]]></author>
			<pubDate>Tue, 22 Mar 2022 16:47:58 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=35345#p35345</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Runit - sym-linking sv]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=35342#p35342</link>
			<description><![CDATA[<p>never used xen, so not sure i understand correctly, is there a xen runscript available that is not working? <br />if you want to use the sysv script maybe this helps : <a href="https://salsa.debian.org/runit-team/runit-services/-/blob/master/debian/README" rel="nofollow">https://salsa.debian.org/runit-team/run … ian/README</a><br />* readme mentions how to switch from sysv script first then how to switch back.. you probably want the latter (?)</p><p>2c</p>]]></description>
			<author><![CDATA[dummy@example.com (xinomilo)]]></author>
			<pubDate>Tue, 22 Mar 2022 15:41:43 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=35342#p35342</guid>
		</item>
		<item>
			<title><![CDATA[[SOLVED] Runit - sym-linking sv]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=35341#p35341</link>
			<description><![CDATA[<p>xen services seem a bit tricky to set up as it does some setting up and then runs 3 daemons.<br />If the OS is not running under the Xen hypervisor, then the SysV init script exits.<br />When I try and do this under Runit, the run script exits, looping once a second.</p><p>Can I get Runit to run the old SysV init script?</p><p>The man page says :-</p><div class="quotebox"><blockquote><div><p>The sv program can be sym-linked to /etc/init.d/ to provide an LSB init script interface. The service to be controlled then is specified by the base name of the ‘‘init script’’.</p></div></blockquote></div><p>I don&#039;t know how to interpret that, so I&#039;ll tried this :-</p><div class="codebox"><pre><code>cd /etc/service
ln -s /usr/bin/sv xen
ls -alF xen
lrwxrwxrwx 1 root root   11 Mar 22 10:32 xen -&gt; /usr/bin/sv*</code></pre></div><p>and the xen script exists in /etc/init.d</p><div class="codebox"><pre><code>ls -alF /etc/init.d/xen
-rwxr-xr-x 1 root root 7929 Jul 10  2021 /etc/init.d/xen*</code></pre></div><p>Test to see if it works :-</p><div class="codebox"><pre><code>sv status xen
fail: xen: unable to change to service directory: not a directory</code></pre></div><p>So, no, that is not the way to do it and it may well be that this would never do what I was after,<br />but I really don&#039;t understand the man page bit about sym-linking to /etc/init.d. Does anyone?</p>]]></description>
			<author><![CDATA[dummy@example.com (Geoff 42)]]></author>
			<pubDate>Tue, 22 Mar 2022 14:48:20 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=35341#p35341</guid>
		</item>
	</channel>
</rss>
