From owner-freebsd-stable@FreeBSD.ORG Sat Jun 9 13:42:25 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 09D381065687 for ; Sat, 9 Jun 2012 13:42:25 +0000 (UTC) (envelope-from adams-freebsd@ateamsystems.com) Received: from fss.sandiego.ateamservers.com (fss.sandiego.ateamservers.com [69.55.229.149]) by mx1.freebsd.org (Postfix) with ESMTP id 8D4F38FC1C for ; Sat, 9 Jun 2012 13:42:24 +0000 (UTC) Received: from [192.168.15.220] (unknown [118.175.84.92]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by fss.sandiego.ateamservers.com (Postfix) with ESMTPSA id 211D1B9F22; Sat, 9 Jun 2012 09:42:21 -0400 (EDT) Message-ID: <4FD352B3.6080805@ateamsystems.com> Date: Sat, 09 Jun 2012 20:42:11 +0700 From: Adam Strohl User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: Sami Halabi References: <201206091035.q59AZWFB058742@lurza.secnetix.de> <20120609122457.GS13609@albert.catwhisker.org> <20120609123626.GT13609@albert.catwhisker.org> <20120609130528.GU13609@albert.catwhisker.org> <4FD35055.1030809@ateamsystems.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: su problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jun 2012 13:42:25 -0000 On 6/9/2012 20:33, Sami Halabi wrote: > its the same as /var/log/messages I assume you mean there is nothing there because it's not the same thing (yes dmesg stuff should get logged into syslog but your system obviously isn't working right so ...). Past that I've been skimming this thread since you posted and I can't think of anything here that would resolve this except that it might be worth a try to have someone ctrl-alt-del it (requires no FreeBSD knowledge, passwords, etc by the person doing it and should gracefully reboot the server). Its a total Hail Mary [pass] though [and probably won't work]. It might lock you out entirely, too. P.S. Beyond this incident obviously setting up a remote console is ideal, IPMI is very worth it, but my guess is you'd have it setup if your MB had it. If you don't have an IPMI module and you happen to have another box there cross-patching their serial consoles to each other so if one goes down you can serial via the other one (ie; server1's com1 to server2's com2, and server2's com1 to server1's com2). You need to set this up as root though so no help now. -- Adam Strohl http://www.ateamsystems.com/