From owner-freebsd-questions@FreeBSD.ORG Thu Mar 4 13:12:33 2004 Return-Path: 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 0088C16A4CE for ; Thu, 4 Mar 2004 13:12:33 -0800 (PST) Received: from smtp01.mrf.mail.rcn.net (smtp01.mrf.mail.rcn.net [207.172.4.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id D643A43D31 for ; Thu, 4 Mar 2004 13:12:32 -0800 (PST) (envelope-from gerard-seibert@rcn.com) Received: from 207-237-110-41.c3-0.crm-ubr4.crm.ny.cable.rcn.com ([207.237.110.41] helo=localhost) by smtp01.mrf.mail.rcn.net with esmtp (Exim 3.35 #4) id 1Az08u-00020H-00 for freebsd-questions@freebsd.org; Thu, 04 Mar 2004 16:12:32 -0500 Date: Thu, 4 Mar 2004 16:12:44 -0500 (Eastern Standard Time) From: Gerard Seibert To: freebsd-questions Message-ID: X-X-Sender: beerstud@spamcop.net@mail.cesmail.net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Error Msg X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Mar 2004 21:12:33 -0000 I am using FreeBSD 5.2.1-RELEASE (GENERIC) #0: MON FEB 23 29:45:55 GMT 2004 I just recently posted about a problem I was having logging into my computer. I eventually was able to log in. I deleted the existing user and subsequently recreated the user. I also had to delete the group as well to complete the operation. However, although I can access my system, the following error message appears when I do an su command. This is the error message: Mar 4 15:52:42 BudMan su: _secure_path: /usr/home/ges/.login_conf is not owed by root The following error message likes to pop up at various times also: Mar 4 15:55:01 BudMan cron[541]: _secure_path: /usr/home/ges/.login_conf is not owned by root The time and date obviously change upon each new occurrence of the message, as well as the number following 'cron'. I have read the man on "_secure_path" but I have no idea what I am supposed to do to correct this problem. Even more mysterious is that this problem and several others only surfaced after installing KDE 3.2. I welcome any assistance someone can afford me, Thanks! Gerard Seibert gerard-seibert@rcn.com ICQ: 95653152