https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082011-01-24T01:16:04ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #1963: ininite rc loophttps://bugs.dragonflybsd.org/issues/1963?journal_id=95032011-01-24T01:16:04Zjustin
<ul></ul><p>On Sun, January 23, 2011 9:50 am, Matthias Rampke wrote:</p>
<blockquote>
<p>I've been setting up a DF-BSD home server. After compiling netatalk,<br />avahi, and some convenience tools (sudo, vim, screen, zsh and<br />pkg_rolling-replace, I think) I wanted to reboot.</p>
<p>Now the machine keeps repeating some part of the boot process (see<br />screenshot at [1]). There's a short delay after "loading devfs rules";<br />when I press ctrl+c then I can break the cycle.</p>
<p>Subsequent actions are taken as often as the cycle ran (with some<br />services complaining that they're already running, other failing to<br />bind to ports etc.).</p>
</blockquote>
<p>Boot from a install CD - you can mount the drives at that point and either<br />continue untangling the server or copy off any config files you want to<br />save, and reinstall. In terms of absolute time, it may be faster to just<br />start over if you don't have to do much reconfiguring. (though be careful<br />to not put yourself in the same loop again...)</p> DragonFlyBSD - Bug #1963: ininite rc loophttps://bugs.dragonflybsd.org/issues/1963?journal_id=95052011-01-24T05:25:38Zc.turner
<ul></ul><p>On Sun, Jan 23, 2011 at 03:50:24PM +0100, Matthias Rampke wrote:</p>
<blockquote>
<p>PS: concerning the symlinking: I know this is bad, and may well have<br />caused this, but I think it <strong>should</strong> work (because without a<br />corresponding entry in rc.conf, each script should be a noop) and it<br /><strong>did</strong> work very well on NetBSD.</p>
</blockquote>
<p>As I recall from 'fiddling' previously I think the rc.d 'rcorder'<br />dependency scan happens before the filesystems are mounted - so all the<br />rc scripts need to physically be on '/' - so I'd definately suggest to<br />try copying the related scripts instead of symlinking here.</p> DragonFlyBSD - Bug #1963: ininite rc loophttps://bugs.dragonflybsd.org/issues/1963?journal_id=95062011-01-24T05:50:36Zmatthiasr
<ul></ul><p>On Sun, Jan 23, 2011 at 22:23, Chris Turner<br /><<a class="email" href="mailto:c.turner@199technologies.org">c.turner@199technologies.org</a>> wrote:</p>
<blockquote>
<p>As I recall from 'fiddling' previously I think the rc.d 'rcorder'<br />dependency scan happens before the filesystems are mounted - so all the<br />rc scripts need to physically be on '/' - so I'd definately suggest to<br />try copying the related scripts instead of symlinking here.</p>
</blockquote>
<p>Sorry this wasn't clear enough: I moved all the scripts from<br />/usr/pkg/share/examples/rc.d to /etc/rc.d and then made the former a<br />symlink pointing to the latter just to ensure all future rc.d scripts<br />would end up there as well. After the whole mess happened I undid<br />this; the /etc/rc.d is now identical to /usr/src/etc/rc.d (i.e. for<br />the time being, pkgsrc-installed rc scripts are out of the way); still<br />no change.</p>
<p>I still have no idea <strong>what</strong> exactly could be messed up; from the<br />symptoms it seems that something in the rc process keeps starting the<br />whole process again and again - until I hit ctrl-c, at which point all<br />these processes continue in parallel. Where could this happen?</p>
<p>Regards, M.</p> DragonFlyBSD - Bug #1963: ininite rc loophttps://bugs.dragonflybsd.org/issues/1963?journal_id=95072011-01-24T06:03:07Zy0n3t4n1
<ul></ul><p>On Sun, Jan 23, 2011 at 03:50:24PM +0100, Matthias Rampke wrote:</p>
<blockquote>
<p>I have symlinked /usr/pkg/etc to /etc and I had linked<br />/usr/pkg/share/examples/rc.d to /etc/rc.d, although I have tried to<br />untangle the latter (which didn't help). Comparing /etc/rc.d with</p>
</blockquote>
<p>This would cause loop because /etc/rc.d/localdaemons tries to scan<br />$local_startup, which contains /usr/pkg/etc/rc.d, which points to<br />/etc/rc.d on your machine. Then there's /usr/pkg/etc/rc.d/localdaemons,<br />which tries to start the things under /usr/pkg/etc/rc.d...</p>
<p>So if you'd like to keep the current configuration, you need to set<br />local_startup=NO in /etc/rc.conf.</p> DragonFlyBSD - Bug #1963: ininite rc loophttps://bugs.dragonflybsd.org/issues/1963?journal_id=95082011-01-24T06:32:11Zmatthiasr
<ul></ul><p>On Sun, Jan 23, 2011 at 23:03, YONETANI Tomokazu (via DragonFly issue tracker)</p>
<blockquote>
<p>On Sun, Jan 23, 2011 at 03:50:24PM +0100, Matthias Rampke wrote:</p>
<blockquote>
<p>I have symlinked /usr/pkg/etc to /etc</p>
</blockquote>
<p>This would cause loop because /etc/rc.d/localdaemons tries to scan<br />$local_startup, which contains /usr/pkg/etc/rc.d</p>
</blockquote>
<p>I wasn't aware of that.</p>
<blockquote>
<p>local_startup=NO in /etc/rc.conf</p>
</blockquote>
<p>This fixed it. Thanks a lot and sorry for the disturbance.</p>