From nobody@FreeBSD.ORG Fri Jun 18 06:37:13 1999
Return-Path: <nobody@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
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: The ctype locales print an error message at login when LC_CTYPE is set.
X-Send-Pr-Version: www-1.0

>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:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jun 18 06:40:01 PDT 1999
>Closed-Date:    Fri Jul 20 15:55:58 PDT 2001
>Last-Modified:  Fri Jul 20 15:56:58 PDT 2001
>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:
State-Changed-From-To: open->closed 
State-Changed-By: mike 
State-Changed-When: Fri Jul 20 15:55:58 PDT 2001 
State-Changed-Why:  

I can't reproduce this bug in a newer version of FreeBSD.  So I 
assume this bug is dead. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=12272 
>Unformatted:
