<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="https://dev1galaxy.org/extern.php?action=feed&amp;tid=6237&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / Upgrading to Daedalus running runit-init]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=6237</link>
		<description><![CDATA[The most recent posts in Upgrading to Daedalus running runit-init.]]></description>
		<lastBuildDate>Mon, 18 Dec 2023 13:58:33 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: Upgrading to Daedalus running runit-init]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=46326#p46326</link>
			<description><![CDATA[<div class="quotebox"><blockquote><div><p>Maybe that should be &#039;chown -R &quot;$USER:$GROUP&quot; &quot;$LOG&quot;&#039; to sort out the log files themselves, as well as the directory?</p></div></blockquote></div><p>it was like that (chown -R) but the recursive option was removed due to symlink attacks [1] risk. But anyway I think the underlying issue is that I can&#039;t force a change in the log runscript (it&#039;s a conffile under /etc/) so there will always be a chance of a mismatch.<br />I&#039;ll drop an entry as NEWS file for runit to warn users.</p><p>Lorenzo<br />[1] For example <a href="https://github.com/OpenRC/opentmpfiles/issues/4" rel="nofollow">https://github.com/OpenRC/opentmpfiles/issues/4</a></p>]]></description>
			<author><![CDATA[dummy@example.com (Lorenzo)]]></author>
			<pubDate>Mon, 18 Dec 2023 13:58:33 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=46326#p46326</guid>
		</item>
		<item>
			<title><![CDATA[Re: Upgrading to Daedalus running runit-init]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=46250#p46250</link>
			<description><![CDATA[<p>Thank you for that.</p><p>I also had to sort out the ownership of the files themselves, <span class="bbc">current</span> and <span class="bbc">lock</span>, but it is now running happily.</p><p>Someone here had worked out a run file that needed very little customisation between services, so my log/run file now looks like :-</p><div class="codebox"><pre><code>#!/bin/sh

NAME=ssh
LOG=&quot;/var/log/runit/$NAME&quot;
USER=&quot;_runit-log&quot;
GROUP=&quot;adm&quot;

chown &quot;$USER:$GROUP&quot; &quot;$LOG&quot;
chmod 750 &quot;$LOG&quot;

exec chpst -u &quot;$USER&quot; svlogd -tt &quot;$LOG&quot;</code></pre></div><p>Maybe that should be &#039;chown -R &quot;$USER:$GROUP&quot; &quot;$LOG&quot;&#039; to sort out the log files themselves, as well as the directory?</p><p>Geoff</p>]]></description>
			<author><![CDATA[dummy@example.com (Geoff 42)]]></author>
			<pubDate>Fri, 15 Dec 2023 16:29:10 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=46250#p46250</guid>
		</item>
		<item>
			<title><![CDATA[Re: Upgrading to Daedalus running runit-init]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=46222#p46222</link>
			<description><![CDATA[<p>Hi Geoff,</p><div class="quotebox"><blockquote><div><p>in /var/log/runit current and lock were both owned by &quot;_runit-log adm&quot; in the subdirectories acpid/ and ssh/<br />This was probably some historic set up error, but :-</p><p>cd /var/log/runit<br />chown runit-log:runit-log acpid/current <br />chown runit-log:runit-log acpid/lock <br />chown runit-log:runit-log ssh/current <br />chown runit-log:runit-log ssh/lock </p><p>soon had that fixed and after the next reboot the runsvdir command line contains the expected, clean line of dots.</p></div></blockquote></div><p>Actually, &#039;runit-log&#039; is being dropped and the &#039;_runit-log&#039; user is the right one. According to Debian policy users created by<br />packages should begin with _ to avoid confusion with real (uman) users. I thought I got this right but evidently I&#039;ve missed<br />something, sorry <img src="https://dev1galaxy.org/img/smilies/sad.png" width="15" height="15" alt="sad" /><br />I recommend to update the log/run script of acpid and ssh with the one that is currently shipped (instead of changing permission<br />of current/lock), for example</p><p>cat /etc/sv/ssh/log/run</p><div class="codebox"><pre><code>#!/bin/sh
chown _runit-log:adm &#039;/var/log/runit/ssh&#039;
chmod 750 &#039;/var/log/runit/ssh&#039;
exec chpst -u _runit-log svlogd -tt &#039;/var/log/runit/ssh&#039;</code></pre></div><p>and then do</p><div class="codebox"><pre><code>sv e ssh</code></pre></div><p>to fix the error</p>]]></description>
			<author><![CDATA[dummy@example.com (Lorenzo)]]></author>
			<pubDate>Thu, 14 Dec 2023 19:18:09 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=46222#p46222</guid>
		</item>
		<item>
			<title><![CDATA[Upgrading to Daedalus running runit-init]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=46173#p46173</link>
			<description><![CDATA[<p>My Chimaera system has been running for a long time and has used <span class="bbc">runit</span> and <span class="bbc">runit-init</span>.<br />I was going to upgrade to Daedalus while having runit and not reverting to SysV init.<br />I simply followed the standard instructions.</p><p><a href="https://www.devuan.org/os/documentation/install-guides/daedalus/upgrade-to-daedalus" rel="nofollow">https://www.devuan.org/os/documentation … o-daedalus</a></p><div class="codebox"><pre><code>apt update
apt upgrade
apt full-upgrade
apt autoremove</code></pre></div><p>edit <span class="bbc">/etc/apt/sources.list</span> - adding <span class="bbc">non-free-firmware</span> as well as changing chimaera to daedalus</p><div class="codebox"><pre><code>deb http://deb.devuan.org/merged daedalus main non-free-firmware non-free contrib
deb http://deb.devuan.org/merged daedalus-updates main non-free-firmware non-free contrib
deb http://deb.devuan.org/merged daedalus-security main non-free-firmware non-free contrib
# deb http://deb.devuan.org/merged daedalus-backports main non-free-firmware non-free contrib</code></pre></div><div class="codebox"><pre><code>apt update</code></pre></div><p>Now kill xscreensaver. The suggested &quot;killall xscreensaver&quot; did not work so I resorted to ps to get the pid and then :-</p><div class="codebox"><pre><code>kill -TERM 24860 # in this case!</code></pre></div><div class="codebox"><pre><code>apt upgrade
apt full-upgrade</code></pre></div><p>It asks about stopping and restarting some processes. Of these <span class="bbc">vsftpd</span> failed to restart. This was due to an historic misconfiguration!</p><p>I think that it took about 1.5 to 2 hours to finish. Then the tidy up.</p><div class="codebox"><pre><code>apt autoremove --purge
apt autoclean</code></pre></div><p>df -h / reported :-</p><div class="codebox"><pre><code>20G 15G 4.2G 78%</code></pre></div><p>before the upgrade and now</p><div class="codebox"><pre><code>20G 17G 2.7G 86%</code></pre></div><p>This seems to imply that Daedalus is taking up 1.5G more than Chimaera.<br />This will of course depend on what you have installed! I have Flightsimulator which does take up a bit of disk space!</p><p>I rebooted and it worked.<br />A had to do bit of fiddling with my dual monitors, but that is not really to do with Daedalus or runit.</p><p>runsvdir command line errors<br />===================</p><p>When I ran &quot;ps axjf&quot; I noticed that the command line of runsvdir was not the expected line of dots, but was carrying some error messages.</p><p><span class="bbc">ps axjf|grep runsvdir</span> reports :-</p><div class="quotebox"><blockquote><div><p>runsvdir -P /etc/service log: tional log directories. svlogd: warning: unable to lock directory: /var/log/runit/ssh: access denied svlogd: fatal: no functional log directories. svlogd: warning: unable to lock directory: /var/log/runit/ssh: access denied svlogd: fatal: no functional log directories. svlogd: warning: unable to lock directory: /var/log/runit/acpid: access denied svlogd: fatal: no functional log directories.</p></div></blockquote></div><p>in /var/log/runit <span class="bbc">current</span> and <span class="bbc">lock</span> were both owned by &quot;_runit-log adm&quot; in the subdirectories acpid/ and ssh/<br />This was probably some historic set up error, but :-</p><div class="codebox"><pre><code>cd /var/log/runit
chown runit-log:runit-log acpid/current 
chown runit-log:runit-log acpid/lock 
chown runit-log:runit-log ssh/current 
chown runit-log:runit-log ssh/lock </code></pre></div><p>soon had that fixed and after the next reboot the <span class="bbc">runsvdir</span> command line contains the expected, clean line of dots.</p><p>NTP<br />===</p><p>ntp has been replaced by ntpsec.</p><p>After the upgrade my set up started <span class="bbc">ntpsec</span> and then <span class="bbc">runit</span> tried to start <span class="bbc">ntp</span> and failed, but looped when it noticed that an ntp service was already running (and was logging it...)</p><p>I needed to sort out ntpsec and disable init.d/ntp. I stopped ntp until I had it sorted.</p><p>I edited <span class="bbc">/etc/sv/ntp/run</span> to contain :-</p><div class="codebox"><pre><code>#!/bin/sh -eu
exec 2&gt;&amp;1

sv start dbus || exit 1

DAEMON=/usr/sbin/ntpd
NTPD_USER=&quot;ntpsec:ntpsec&quot;
NTPD_OPTS=&quot;-n -N -g -u $NTPD_USER&quot;
NTPD_OPTS=&quot;-c /etc/ntpsec/ntp.conf $NTPD_OPTS&quot;

exec $DAEMON $NTPD_OPTS</code></pre></div><p>This now runs happily...</p><div class="codebox"><pre><code>sv up ntp
sv status ntp
run: ntp: (pid 15388) 1101s; run: log: (pid 1935) 6879s</code></pre></div><p>To stop the init.d versions getting started (my runit service is called &quot;ntp&quot; so I disabled both ntp and ntpsec) :-</p><div class="codebox"><pre><code>update-rc.d ntp disable
update-rc.d ntpsec disable</code></pre></div><p>The ntp service is now running smoothly under runit.</p><p>I will report success with postgresql separately.</p><p>Geoff</p>]]></description>
			<author><![CDATA[dummy@example.com (Geoff 42)]]></author>
			<pubDate>Wed, 13 Dec 2023 11:13:41 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=46173#p46173</guid>
		</item>
	</channel>
</rss>
