On Fri, 8 Jun 2001, Terry Lambert wrote:
> Matthew Jacob wrote:
>
> [ ... FreeBSD Legato client coredump ... ]
>
> > This is really a 'ports' issue...
>
> No, it's an Advocacy and commercial support of FreeBSD issue.
>
>
> > I don't know why this happens. It was suggested that it
> > was pr
Matthew Jacob wrote:
[ ... FreeBSD Legato client coredump ... ]
> This is really a 'ports' issue...
No, it's an Advocacy and commercial support of FreeBSD issue.
> I don't know why this happens. It was suggested that it
> was probably a bug in nsrexecd- malloc maybe. Possibly.
> It doesn't al
This is really a 'ports' issue...
I don't know why this happens. It was suggested that it was probably a bug in
nsrexecd- malloc maybe. Possibly. It doesn't always happen, as it's happily
running right now on at least one i386 running -current (June 3) and one alpha
(June 2)- but don't let the
Gentlemen,
I try to run (any) legato client on fBSD -current and so far had no
success. All clients i tried (nwclient from ports, nwclient from release
3) exit on a siganl 11:
luna /boot/kernel/kernel: pid 16940 (nsrexecd), uid 0: exited on signal
11 (core dumped)
Strange enough even the "orig
