From owner-freebsd-questions@FreeBSD.ORG Fri Jul 7 18:56:10 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2FA4F16A4DD for ; Fri, 7 Jul 2006 18:56:10 +0000 (UTC) (envelope-from atom.powers@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3DEE43D53 for ; Fri, 7 Jul 2006 18:56:09 +0000 (GMT) (envelope-from atom.powers@gmail.com) Received: by py-out-1112.google.com with SMTP id i75so500645pye for ; Fri, 07 Jul 2006 11:56:08 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=pC99ri18+d1rH1XdDz462Du8KSmTKCNZd0KPU79G8EIwdzAffIRfhY/R81Ictenei+6/H5w10jO9pzMzSM+V270tOvdFeIr6kT6ndSMkvMjWidBwUq261nYrIbFtLEM7WmCGFuGN5KdD/M+/vKsbRbjEd6X9leqB4pc66PxR1u0= Received: by 10.35.101.9 with SMTP id d9mr2442802pym; Fri, 07 Jul 2006 11:56:08 -0700 (PDT) Received: by 10.35.110.6 with HTTP; Fri, 7 Jul 2006 11:56:08 -0700 (PDT) Message-ID: Date: Fri, 7 Jul 2006 11:56:08 -0700 From: "Atom Powers" To: freebsd-questions@freebsd.org In-Reply-To: <20060707141747.E914.GERARD@seibercom.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060707141747.E914.GERARD@seibercom.net> Subject: Re: Error Message with 'periodic weekly' X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 18:56:10 -0000 On 7/7/06, Gerard Seibert wrote: > I just did a fresh install of FBSD 6.1. When attempting to run: > > periodic weekly > > This error message is displayed: > > Jul 7 14:12:47 seibercom su: _secure_path: /nonexistent/.login_conf is > not owned by uid 65534 First, /nonexistant should probably not exist. It is the home directory of the "nobody" user (uid 65534). I would just kill it `rm -rf /nonexistant` If it *does* exist that may not be a problem, as long as the nobody user does not have a valid shell, but /nonexistant is used by many system accounts so just setting the ACLs on it to `chmod -R nobody:nobody /nonexistant` probably won't help much. -- -- Perfection is just a word I use occasionally with mustard. --Atom Powers--