From owner-freebsd-bugs  Fri Jun 18  6:40: 4 1999
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP id 745241538D
	for <freebsd-bugs@FreeBSD.org>; Fri, 18 Jun 1999 06:40:02 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id GAA95586;
	Fri, 18 Jun 1999 06:40:02 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id B522615378; Fri, 18 Jun 1999 06:37:13 -0700 (PDT)
Message-Id: <19990618133713.B522615378@hub.freebsd.org>
Date: Fri, 18 Jun 1999 06:37:13 -0700 (PDT)
From: jau@iki.fi
To: freebsd-gnats-submit@freebsd.org
X-Send-Pr-Version: www-1.0
Subject: bin/12272: The ctype locales print an error message at login when LC_CTYPE is set.
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         12272
>Category:       bin
>Synopsis:       The ctype locales print an error message at login when LC_CTYPE is set.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jun 18 06:40:01 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator:     Jukka A. Ukkonen
>Release:        3.1
>Organization:
SysOpen Group
>Environment:
FreeBSD 3.1
>Description:
When using tcsh as the login shell the ctype locales pointlessly
print an error message at login time if LC_CTYPE is set.
This is extremely irritating when trying to transfer files using
rcp to a system which suffers from this problem.
The same problem has been there at least since version 2.2.1
through all the revisions to the current 3.1.
>How-To-Repeat:
Set tcsh as your login shell.
Put the line "setenv LC_CTYPE fi_FI.ISO_8859-1" to your .tcshrc file.
Try first rsh to the system where you did these changes.
You should see a garbled error message.
Then try rcp something to the system. This should completely fail
due to the way rcp handles unexpected output from the peer.
>Fix:
Not known yet, but I definitely let you know if/when I find one.


>Release-Note:
>Audit-Trail:
>Unformatted:


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message