>Number:         12332
>Category:       bin
>Synopsis:       /bin/sh misbehaves in single user mode
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Mar 05 01:16:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Tim Rightnour
>Release:        03/01/01<NetBSD-current source date>
>Organization:
	
>Environment:
	
System is NetBSD/alpha kernel current as of 03/01/01, userland as of
02/25/01 (from chuq's snapshot)

>Description:
When working in single usermode, from time to time the shell begins to behave
poorly, making the entire shell unusable.  It responds only to builtin
commands and will not exec any further processes.  It seems to work for awhile
and then some unknown trigger causes it to cease working.  On one occasion
I had been in single-user for awhile, running many commands, executed a ksh
shell.  When exiting the ksh shell, my primary shell was broken.  Another time
I dropped into single-user, ran raidctl -S twice, one for each of my raid
devices.  After the second occurrance.. the shell was useless.

A transcript of one such session is below:
# dmesg | more
tcsetpgrp failed, errno=25
tcsetpgrp failed, errno=25
tcsetpgrp failed, errno=25

# reboot
tcsetpgrp failed, errno=25
tcsetpgrp failed, errno=25

# exit

	
>How-To-Repeat:
Unsure.. different commands trigger it, but are not guaranteed to do so.
	
>Fix:
No idea.
	
>Release-Note:
>Audit-Trail:
>Unformatted: