This patch corrects the following: - Fixes a problem that was caused by the Korn shell running in EMACS mode. When a window was resized with a width that exceeded 160 characters, the next command (or even a return) would cause the ksh utility to core dump. - Corrects a problem which results in a superuser being able to inadvertently bring the system down to single user mode by accidentally killing pid 1 (init) when trying to kill a background job (%1). - Fixes a problem in the csh shell that caused a change in the way wildcard patterns were matched. The problem resulted in the error: Glob aborted - Permission denied - Fixes a problem when builtin variables (ex. TMOUT) are exported as readonly with values > 256. The 'set' command (display all variables) will cause ksh to core dump with the error "stack overflow". - Fixes a memory management problem that occurs on systems running the Korn shell. Incorrect results occur when the length of the parameter to the echo command is altered. - Fixes a problem with /usr/bin/ksh and the named-pipe (FIFO) communication that is used by applications. - Corrects a problem that was causing ksh to core dump in vi editing mode. ksh was core dumping intermittently when using '.' to repeat a command. - Fixes unexpected logouts and terminal hangups encountered when using the /bin/su command and /bin/ksh as a login shell. - ksh does a segmentation fault and core dumps when displaying a here-document. - Fixes a core dump from ksh. - Corrects the printing of Japanese SJIS strings that are assigned to shell variables in the C shell (csh). - Corrects a problem that may cause ksh to coredump when displaying a large here-document in a ksh script. - Fixes a problem with the Korn shell where data loss occurs when commnds are piped together. - Corrects how the C shell handles 2-byte characters when running in the Japanese SJIS locale. - Fixes a problem in ksh which required 2 SIGTERM signals to be sent to the process when it exec'ed. - Fixes a problem in the C shell (csh) in which a segmentation fault will occur when the user defines an environmental variable which exceeds the 2048 character limitation. This limit has been lengthened to 8192 characters.