DragonFlyBSD

On Sun, January 23, 2011 9:50 am, Matthias Rampke wrote:

I've been setting up a DF-BSD home server. After compiling netatalk,
avahi, and some convenience tools (sudo, vim, screen, zsh and
pkg_rolling-replace, I think) I wanted to reboot.

Now the machine keeps repeating some part of the boot process (see
screenshot at [1]). There's a short delay after "loading devfs rules";
when I press ctrl+c then I can break the cycle.

Subsequent actions are taken as often as the cycle ran (with some
services complaining that they're already running, other failing to
bind to ports etc.).

Boot from a install CD - you can mount the drives at that point and either
continue untangling the server or copy off any config files you want to
save, and reinstall. In terms of absolute time, it may be faster to just
start over if you don't have to do much reconfiguring. (though be careful
to not put yourself in the same loop again...)

On Sun, Jan 23, 2011 at 03:50:24PM +0100, Matthias Rampke wrote:

PS: concerning the symlinking: I know this is bad, and may well have
caused this, but I think it should work (because without a
corresponding entry in rc.conf, each script should be a noop) and it
did work very well on NetBSD.

As I recall from 'fiddling' previously I think the rc.d 'rcorder'
dependency scan happens before the filesystems are mounted - so all the
rc scripts need to physically be on '/' - so I'd definately suggest to
try copying the related scripts instead of symlinking here.

On Sun, Jan 23, 2011 at 22:23, Chris Turner
<c.turner@199technologies.org> wrote:

As I recall from 'fiddling' previously I think the rc.d 'rcorder'
dependency scan happens before the filesystems are mounted - so all the
rc scripts need to physically be on '/' - so I'd definately suggest to
try copying the related scripts instead of symlinking here.

Sorry this wasn't clear enough: I moved all the scripts from
/usr/pkg/share/examples/rc.d to /etc/rc.d and then made the former a
symlink pointing to the latter just to ensure all future rc.d scripts
would end up there as well. After the whole mess happened I undid
this; the /etc/rc.d is now identical to /usr/src/etc/rc.d (i.e. for
the time being, pkgsrc-installed rc scripts are out of the way); still
no change.

I still have no idea what exactly could be messed up; from the
symptoms it seems that something in the rc process keeps starting the
whole process again and again - until I hit ctrl-c, at which point all
these processes continue in parallel. Where could this happen?

Regards, M.

On Sun, Jan 23, 2011 at 03:50:24PM +0100, Matthias Rampke wrote:

I have symlinked /usr/pkg/etc to /etc and I had linked
/usr/pkg/share/examples/rc.d to /etc/rc.d, although I have tried to
untangle the latter (which didn't help). Comparing /etc/rc.d with

This would cause loop because /etc/rc.d/localdaemons tries to scan
$local_startup, which contains /usr/pkg/etc/rc.d, which points to
/etc/rc.d on your machine. Then there's /usr/pkg/etc/rc.d/localdaemons,
which tries to start the things under /usr/pkg/etc/rc.d...

So if you'd like to keep the current configuration, you need to set
local_startup=NO in /etc/rc.conf.

On Sun, Jan 23, 2011 at 23:03, YONETANI Tomokazu (via DragonFly issue tracker)

On Sun, Jan 23, 2011 at 03:50:24PM +0100, Matthias Rampke wrote:

I have symlinked /usr/pkg/etc to /etc

This would cause loop because /etc/rc.d/localdaemons tries to scan
$local_startup, which contains /usr/pkg/etc/rc.d

I wasn't aware of that.

local_startup=NO in /etc/rc.conf

This fixed it. Thanks a lot and sorry for the disturbance.