From owner-freebsd-security Tue May 16 8:46:54 2000 Delivered-To: freebsd-security@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 2522337B92A for ; Tue, 16 May 2000 08:46:51 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e4GGJX405390; Tue, 16 May 2000 09:19:33 -0700 (PDT) Date: Tue, 16 May 2000 09:19:33 -0700 From: Alfred Perlstein To: Frank Tobin Cc: FreeBSD-security Mailing List Subject: Re: pid file for named Message-ID: <20000516091932.J20000@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from ftobin@uiuc.edu on Tue, May 16, 2000 at 06:48:05AM -0500 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Frank Tobin [000516 05:22] wrote: > However, the pid file, /var/run/named.pid, which named tries to write out > one cannot give the proper permissions for, because it resides in a > root-owned directory /var/run. Granted, named writes out this file before > it drops privileges, and doesn't need to re-write this file when it > reloads, even though it tries and complains about not being able to > because it has dropped privileges. Actually there's an evil trick one can use: # cd /var/run # mkdir named # touch named/named.pid # ln -s named/named.pid . # chown named:named named # rm named/named.pid :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message