Xref: utzoo comp.unix.questions:15079 comp.bugs.sys5:1043 comp.unix.microport:3598
Path: utzoo!attcan!uunet!wugate!wuarchive!brutus.cs.uiuc.edu!tut.cis.ohio-state.edu!cica!iuvax!rutgers!att!occrsh!rjd
From: rjd@occrsh.ATT.COM (Randy_Davis)
Newsgroups: comp.unix.questions,comp.bugs.sys5,comp.unix.microport
Subject: Re: ksh and sh
Summary: It will break at(1).
Message-ID: <805@occrsh.ATT.COM>
Date: 21 Jul 89 02:16:57 GMT
References: <372@trevan.UUCP>
Reply-To: rjd@occrsh.UUCP (Randy_Davis)
Followup-To: comp.unix.questions
Organization: AT&T Network & Data Systems, OKC
Lines: 16

In article <372@trevan.UUCP> trevor@trevan.UUCP (trevor) writes:
...
|	Is there anything wrong in changing the name of ksh to sh or
|is there any incompatability.

  It will break the at command, among other things...  When "at" saves your
enviroment for subsequent job execution, it goes through and saves all of
them.  The problem with this is that when the at job is later executed, at
tries to go through and restore all of the enviroment variables, including
the ksh-specific ones, such as RANDOM, PPID, PWD, RANDOM, SECONDS, and _
(last command line).  Now, at this moment I am not sure, but at least one
of these causes the "at" job to crash when it is restoring the enviroment.
It has been a while since I tried it - sorry if my memory is vague...

Randy Davis			UUCP: ...(att.att.com!)ocrjd.att.com!randy
				      ...(att.att.com!)occrsh.att.com!rjd