I have a NetBSD 6 system, with jabberd 2.4.0 (built for netbsd 5 still.
Although binary compat at this level is almost beyond suspicion, I am
rebuilding all packages) . Jabberd mostly works fine, but on boot sm
crashes. I have adjusted sequencing, although in theory it should not
matter (and
Greg Troxel writes:
- On a netbsd-5 i386 box (xen domU) that is otherwise stable, with jabberd
- 2.3.2 and mu-conference 0.8.81, on boot we saw:
-
- Feb 6 05:33:34 foo /netbsd: pid 317 (sm), uid 1001: exited on signal 11 (c
- ore not dumped, err = 13)
- Feb 6 05:34:26 foo /netbsd: pid 540
e...@cirr.com (Eric Schnoebelen) writes:
I've not see anything like that on NetBSD 6_STABLE/alpha. I do
see mu-conference crashing semi-regularly, as well as it
occasionally running away (but not nearly as much after the
last set of patches.)
It's cool you are running this on alpha.
The
On a netbsd-5 i386 box (xen domU) that is otherwise stable, with jabberd
2.3.2 and mu-conference 0.8.81, on boot we saw:
Feb 6 05:33:34 foo /netbsd: pid 317 (sm), uid 1001: exited on signal 11 (core
not dumped, err = 13)
Feb 6 05:34:26 foo /netbsd: pid 540 (mu-conference), uid 1001: exited on
