From owner-freebsd-current@FreeBSD.ORG Wed Apr 30 07:55:28 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ACB8737B401; Wed, 30 Apr 2003 07:55:28 -0700 (PDT) Received: from tao.xtaz.co.uk (pc-62-30-69-139-az.blueyonder.co.uk [62.30.69.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5E0743F75; Wed, 30 Apr 2003 07:55:27 -0700 (PDT) (envelope-from matt@xtaz.co.uk) Received: from webmail.xtaz.co.uk (localhost [127.0.0.1]) by tao.xtaz.co.uk (Postfix) with SMTP id 6D6508FCFD; Wed, 30 Apr 2003 15:55:26 +0100 (BST) Received: from 193.35.129.161 (SquirrelMail authenticated user matt) by webmail.xtaz.co.uk with HTTP; Wed, 30 Apr 2003 15:55:26 +0100 (BST) Message-ID: <24700.193.35.129.161.1051714526.squirrel@webmail.xtaz.co.uk> In-Reply-To: <20030430114307.GC22733@madman.celabo.org> References: <20030428075916.GA53857@myhakas.internal><20030428075916.GA53857@myhak as.internal><20030428190209.A21656@dilbert.robbins.dropbear.id.au><87o f2rexxd.fsf@boggy.acest.tutrp.tut.ac.jp><20030428174751.GA38323@madman .celabo.org> <86adeajfpe.fsf@xa12.heimat.gr.jp><20030429025749.GA49911@madman.celab o.org><20030429025749.GA49911@madman.celabo.org> <86bryqx8w6.fsf@xa12.heimat.gr.jp><87sms0cv13.fsf@boggy.acest.tutrp.tu t.ac.jp> <20030430114307.GC22733@madman.celabo.org> Date: Wed, 30 Apr 2003 15:55:26 +0100 (BST) From: "Matt" To: "Jacques A. Vidrine" User-Agent: SquirrelMail/1.4.0 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal cc: current@freebsd.org Subject: Re: Somethings still up with new NSS? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2003 14:55:29 -0000 Not sure if it is NSS related or not but it looks suspicious. When bind starts it gets set to user/group bind as normal, but: [root@tao named]# ps waux | grep named bind 50019 0.0 0.8 2772 2120 ?? Ss 3:28PM 0:00.24 /usr/sbin/named -u bind -g bind [root@tao named]# ndc reload Reload initiated. [root@tao named]# ps waux | grep named bind 50019 0.0 0.8 2772 2120 ?? Ss 3:28PM 0:00.26 /usr/sbin/named -u bind -g bind However /var/log/messages reports: Apr 30 15:52:13 tao named[50019]: couldn't create pid file '/var/run/named.pid' [root@tao named]# ls -al /var/run/named.pid -rw-r--r-- 1 bind bind 6 Apr 30 15:28 /var/run/named.pid The file was created when I actually ran /usr/sbin/named -u bind -g bind but an ndc reload seems to not setuid properly I guess? -- email: matt@xtaz.co.uk - web: http://xtaz.co.uk/ Hardware, n.: The parts of a computer system that can be kicked.