From owner-freebsd-questions@FreeBSD.ORG Wed Apr 19 14:07:18 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 B0D0216A403 for ; Wed, 19 Apr 2006 14:07:18 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail2.sea5.speakeasy.net (mail2.sea5.speakeasy.net [69.17.117.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BA7543D46 for ; Wed, 19 Apr 2006 14:07:18 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 21748 invoked from network); 19 Apr 2006 14:07:17 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail2.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 19 Apr 2006 14:07:17 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id E94C428423; Wed, 19 Apr 2006 10:07:16 -0400 (EDT) Sender: lowell@be-well.ilk.org To: dharam paul To: freebsd-questions@freebsd.org References: <20060418144458.18732.qmail@web8903.mail.in.yahoo.com> From: Lowell Gilbert Date: 19 Apr 2006 10:07:16 -0400 In-Reply-To: <20060418144458.18732.qmail@web8903.mail.in.yahoo.com> Message-ID: <44mzehr757.fsf@be-well.ilk.org> Lines: 19 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Subject: Re: can not su X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 14:07:18 -0000 Please don't top-post. dharam paul writes: > You are right to say that /var/lib/ does not exist > that is what logrotation through webmin said. So I > created the folder '/var/lib/ and when logrotate > furhter gave different errors, I removed the folder > '/var/lib/' Okay, so it sounds like /var/lib is unrelated to the problem. So what you have said about the problem is that you can't log in as root or su to root. That's really not enough for anybody to help solve the problem, except by sheer guessing. Were you able to login as root in the past? What else did you change in the meantime? You could always reboot and use single-user mode to examine the logs, the password file, etc.