From owner-freebsd-hackers@FreeBSD.ORG Wed May 24 12:51:54 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3DFA16A498 for ; Wed, 24 May 2006 12:51:54 +0000 (UTC) (envelope-from jhein@timing.com) Received: from Daffy.timing.com (w.timing.com [206.168.13.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37B8743D6E for ; Wed, 24 May 2006 12:51:46 +0000 (GMT) (envelope-from jhein@timing.com) Received: from gromit.timing.com (gromit.timing.com [206.168.13.209]) by Daffy.timing.com (8.13.1/8.12.8) with ESMTP id k4OCpjEV012982; Wed, 24 May 2006 06:51:45 -0600 (MDT) (envelope-from jhein@timing.com) Received: from gromit.timing.com (localhost [127.0.0.1]) by gromit.timing.com (8.13.6/8.13.4) with ESMTP id k4OCpjDJ024602; Wed, 24 May 2006 06:51:45 -0600 (MDT) (envelope-from jhein@gromit.timing.com) Received: (from jhein@localhost) by gromit.timing.com (8.13.6/8.13.6/Submit) id k4OCpjHm024599; Wed, 24 May 2006 06:51:45 -0600 (MDT) (envelope-from jhein) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17524.22241.137972.599803@gromit.timing.com> Date: Wed, 24 May 2006 06:51:45 -0600 From: John E Hein To: Artem Kazakov In-Reply-To: <1148468449.1745.27.camel@tyoma.linac.kek.jp> References: <1148468449.1745.27.camel@tyoma.linac.kek.jp> X-Mailer: VM 7.19 under Emacs 21.3.1 X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on Daffy.timing.com X-Virus-Status: Clean Cc: FreeBSD Hackers Subject: Re: tcsh & nss_ldap problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 12:52:04 -0000 Artem Kazakov wrote at 20:00 +0900 on May 24, 2006: > I don't know if this should go here, point me to the right place. > But it looks like a problem (bug?) in tcsh. That report and the link to the PR should be plenty of information to ship off to: Tcsh-Bugs@mx.gw.com (see also http://mx.gw.com/mailman/listinfo/tcsh-bugs)