From owner-freebsd-security Wed Dec 16 04:39:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA06654 for freebsd-security-outgoing; Wed, 16 Dec 1998 04:39:09 -0800 (PST) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA06634; Wed, 16 Dec 1998 04:39:03 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.1/8.9.1) id NAA00529; Wed, 16 Dec 1998 13:38:51 +0100 (CET) (envelope-from des) To: "D. Rock" Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: kmem, tty, bind security enhancements commit. References: <199812010551.VAA02953@apollo.backplane.com> <36778044.A8FDC865@cs.uni-sb.de> From: Dag-Erling Smorgrav Date: 16 Dec 1998 13:38:51 +0100 In-Reply-To: "D. Rock"'s message of "Wed, 16 Dec 1998 10:41:24 +0100" Message-ID: Lines: 16 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "D. Rock" writes: > Only a small glitch: > % ndc reload > now gives you everytime an > named[24812]: couldn't create pid file '/var/run/named.pid' > error message to syslog. > It isn't a big deal, because on reload the pid doesn't change. But > it's still annoying. There are worse glitches. Interface scanning no longer works, and cache dumping no longer works unless you create a directory writeable by bind and configure named to use that. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message