somehow he got his YP and DNS screwed up and nslookup $h was dealing with h = ""
which was doing nslookup "", which is bad and hangs boots.  be more careful
by doing echo $h | nslookup instead.

ok otto deraadt

ok millert@

and freebsd, apparently written by torek, the man we never see anymore;
submitted by jcs, but he is not around right now for the libc major crank
so i sneak it in for him

useful feedback and ok deraadt@

From: FreeBSD by Constantin S. Svintsoff <kostik (at) iclub.nsu.ru>
ok otto@ millert@

with a specific manpage reference.

limited to power change events and battery status retrieval.
ok deraadt@ mickey@

on error.

who have machines that hit swap a lot.  decided after survey of developers,
we found that most turned this on.  ok various

Alexander von Gernler <grunk@pestilenz.org>

ssize_t
From: Alexander von Gernler <grunk@pestilenz.org>

From: Jason Crawford <jasonrcrawford@gmail.com>, whitespace fixes me

tell people where to look; idea from miod

- Handle errors from syscalls better
- Prevent curtime.tv_usec from being negative for negative offsets.
- Don't claim to have done settimeofday if it fails.
ok henning@

guaranteed that its res_init() call was done once before fork etc...
that is no longer the case. call res_init() in main() early.

there are some bytes left (less than an imsg header, or less than the
imsg header len field says) we copy it to the very beginning of the buffer.
use memmove instead of memcpy since it is not guaranteed that there's no
overlap. while memcpy on OpenBSD is safe, it might not elsewhere, and
we want our code to be correct anyways.
funny enough theo and I talked at length about that last week in dublin,
and I said I believe I had no memcpys with the chance of overlap in ntpd/bgpd -
well, here is one, and Alexander von Gernler <grunk@pestilenz.org> pointed
me to it.

systems since it still has all the filesystems for vnd usage and thus
does not save much memory...
ok deraadt@

do so when
-we tried to send at least one query (that is the change)
-we could not send ou a single one without failure (this was already in
place but catched too much)
problem independently noticed by nick and danh, ok mickey danh, testing by
many