I haven't been paying attention to mail on these LDOMs. Thanks for the
heads up. Output looks good.
>From r...@puffyfive.ldom.openbsd.local Sat Jul 1 14:07:05 2017
Delivered-To: r...@puffyfive.ldom.openbsd.local
From: Charlie Root <r...@puffyfive.ldom.openbsd.local>
To: r...@puffyfive.ldom.openbsd.local
Subject: puffyfive.ldom.openbsd.local Kernel relink info
Kernel has been relinked and is active on next reboot
SHA256 (/bsd) =
8c55d2fa748ecb0b44db1169c38a514f5364bd47d8e331f3671617bdebdf7116
Relink log:
sh makegap.sh 0x00000000
ld -n -T ld.script --warn-common -nopie -o newbsd ${SYSTEM_HEAD} vers.o
${OBJS}
text data bss dec hex
6572680 2115208 676768 9364656 8ee4b0
mv newbsd newbsd.gdb
strip -S -o newbsd newbsd.gdb
mv -f newbsd bsd
cmp -s bsd /bsd || ln -f /bsd /obsd
umask 077 && cp bsd /nbsd && mv /nbsd /bsd && sha256 -h
/var/db/kernel.SHA256 /bsd
&
On Sat, Jul 1, 2017 at 1:54 PM, Theo de Raadt <dera...@openbsd.org> wrote:
> > I've put the snapshot LDOM through some paces with each snapshot: high
> CPU
> > load, networking, and heavy filesystem utilization. It's every bit as
> solid
> > as the other LDOMs. I have only seen the "relinking" message at the end
> of
> > snapshot upgrades, but due to /bsd changing upon each reboot, I believe
> it
> > is behaving exactly as Theo described.
>
> It sends a mail to root. For now. Later, we'll switch to a single
> syslog entry.
>
