Geoff Wing writes:
> Unfortunately my machine is mostly headless and I can't get dmesg saved
> after reboot.
> [...]
> Is "bt;sync" better?
If you want the dmesg output, you do want the core dump:
# dmesg -N /var/crash/netbsd.42 -M /var/crash/netbsd.42.core
...and for
On Wed, Dec 28, 2016 at 11:26:10AM -0800, Brian Buhrow wrote:
> Hello. I'm sure this problem is pilot error on my part, but I'm
> having trouble figuring out where the build process is picking up the user
> postgres in the destination build environent.
> I'm hosting the build on a
Updating src tree:
P src/distrib/sets/lists/comp/ad.mips
P src/external/bsd/top/dist/top.1.in
P src/share/man/man2/siginfo.2
P src/share/man/man4/ixg.4
P src/share/man/man9/ethersubr.9
P src/sys/arch/evbmips/cavium/machdep.c
P src/sys/arch/evbmips/conf/ERLITE
P
In article <20161228085903.ga1...@primenet.com.au>,
Geoff Wing wrote:
>Hi,
>with -current today, when I "/etc/rc.d/ipfilter start" on amd64 it panics in
>
>sys/net/pfil.c:
>pfil_add_hook(pfil_func_t func, void *arg, int flags, pfil_head_t *ph)
>...
>KASSERT((flags &
Hello. I'm sure this problem is pilot error on my part, but I'm
having trouble figuring out where the build process is picking up the user
postgres in the destination build environent.
I'm hosting the build on a NetBSD-5.2/i386 system. The build command looks
like:
./build.sh -D
Hi,
on an amd64 machine, I was getting the child sshd process seg-faulting
(I believe after dropping privileges but I wasn't getting a coredump) when
trying to accept a connection (``sshd -d -d -d'' wasn't really helpful).
It had three legacy lines in its sshd_config:
HostKey
Hi,
with -current today, when I "/etc/rc.d/ipfilter start" on amd64 it panics in
sys/net/pfil.c:
pfil_add_hook(pfil_func_t func, void *arg, int flags, pfil_head_t *ph)
...
KASSERT((flags & ~PFIL_ALL) == 0);
...
Unfortunately my machine is mostly headless and I can't get dmesg saved
after