Date: Mon, 16 Dec 2013 00:23:41 +0100 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: Tim Kientzle <kientzle@freebsd.org> Cc: FreeBSD current <freebsd-current@freebsd.org> Subject: Re: dhclient can't limit bpf descriptor? Message-ID: <20131215232341.GA1343@garage.freebsd.pl> In-Reply-To: <D88167A6-8DE9-40A1-B55C-667776ABB00D@freebsd.org> References: <D88167A6-8DE9-40A1-B55C-667776ABB00D@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 14, 2013 at 12:12:23PM -0800, Tim Kientzle wrote: > Opened up an old VM from a month or so ago (r257910) and dhclient won=E2= =80=99t start. >=20 > Specifically, dhclient complains (when run by root): > =E2=80=9Ccan=E2=80=99t limit bpf descriptor: Bad address=E2=80=9D > and then immediately exits. >=20 > What does this mean? I don=E2=80=99t know anything about the capabiliti= es > framework and certainly haven=E2=80=99t configured it in any way. Maybe your userland and kernel are out of sync? There was backward-incompatible change in Capsicum that could result in error like that (capability rights are now passed as a pointer to a structure and not uint64_t bitfield). --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://mobter.com --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iEYEARECAAYFAlKuOf0ACgkQForvXbEpPzTnfgCgx/Ssrs88reKmI4GqK9BkiPQp hcMAni9qUF0VXVwtibHMWdqY46MTDgti =dy9k -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131215232341.GA1343>