From owner-freebsd-questions@FreeBSD.ORG Mon Sep 12 08:07:31 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6AE5A106564A for ; Mon, 12 Sep 2011 08:07:31 +0000 (UTC) (envelope-from i.tanusheff@procreditbank.bg) Received: from mailgate.procreditbank.bg (mailgate.procreditbank.bg [193.26.216.3]) by mx1.freebsd.org (Postfix) with SMTP id 7A1898FC14 for ; Mon, 12 Sep 2011 08:07:30 +0000 (UTC) Received: (qmail 18628 invoked from network); 12 Sep 2011 10:40:48 +0300 Received: from unknown (HELO domino-archive.procreditbank.bg) (10.0.0.60) by 192.168.1.3 with SMTP; 12 Sep 2011 10:40:48 +0300 Received: from domino.procreditbank.bg ([10.0.0.15]) by domino-archive.procreditbank.bg (Lotus Domino Release 8.5.1FP5) with ESMTP id 2011091210404766-4951 ; Mon, 12 Sep 2011 10:40:47 +0300 In-Reply-To: <4E6A0C1F.7090505@visi.com> References: <4E6A0C1F.7090505@visi.com> X-Disclaimed: 1182 To: Paul Keusemann MIME-Version: 1.0 X-KeepSent: E9735D29:0DDC3FE1-C2257909:002A15B6; type=4; flags=0; name=$KeepSent X-Mailer: Lotus Notes Release 8.5.1 September 28, 2009 From: Ivailo Tanusheff Message-ID: Date: Mon, 12 Sep 2011 10:40:47 +0300 X-MIMETrack: Serialize by Router on DOMINO/BULGARIA/PROCREDITBANK(Release 8.5.1FP5|September 29, 2010) at 09/12/2011 10:40:48 AM, Serialize complete at 09/12/2011 10:40:48 AM, Itemize by SMTP Server on DOMINO-ARCHIVE/BULGARIA/PROCREDITBANK(Release 8.5.1FP5|September 29, 2010) at 09/12/2011 10:40:47 AM, Serialize by Router on DOMINO-ARCHIVE/BULGARIA/PROCREDITBANK(Release 8.5.1FP5|September 29, 2010) at 09/12/2011 10:40:47 AM, Serialize complete at 09/12/2011 10:40:47 AM Content-Type: text/plain; charset="US-ASCII" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-questions@freebsd.org, owner-freebsd-questions@freebsd.org Subject: Re: Can't log in as toor since package update 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: Mon, 12 Sep 2011 08:07:31 -0000 I don't really believe that toor user should be used like that - check the handbook for example. You better use normal user or the root itself. In 8.x the described is a normal behaviour. Regards, Ivailo Tanusheff Paul Keusemann Sent by: owner-freebsd-questions@freebsd.org 09.09.2011 16:14 To freebsd-questions@freebsd.org cc Subject Can't log in as toor since package update I use the toor login on my FreeBSD systems to log in with the korn shell. Since August 22, When I try to log in as toor or even when I try to "su - toor", I get logged in as root. For example: ushers# ssh -l toor woodstock Password: Last login: Fri Sep 9 06:30:23 2011 from 172.16.175.216 Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 8.2-RELEASE-p1 (WOODSTOCK) #1: Mon Jul 11 09:05:07 CDT 2011 woodstock# who am i root 0 Sep 9 07:46 woodstock# su - toor woodstock# who am i root 0 Sep 9 07:47 Unfortunately, I haven't tried to log in since a package update I did around August 22, so I didn't notice this problem until now. Does anybody have any idea what might be causing this? -- Paul Keusemann pkeusem@visi.com 4266 Joppa Court (952) 894-7805 Savage, MN 55378 _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" Disclaimer: The information contained in this message is intended solely for the use of the individual or entity to whom it is addressed and to others authorised to receive it. It may contain confidential or legally privileged information. It you are not the intended recipient you are hereby notified that any disclosure, copying, distribution, or taking any action based on the contents of this message is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this e-mail and then delete it from your system. ProCredit Bank is neither liable for the proper and complete transmission for the information contained in this message nor for any delay in its receipt.