From owner-freebsd-ports  Tue May  9 03:29:56 1995
Return-Path: ports-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id DAA09380
          for ports-outgoing; Tue, 9 May 1995 03:29:56 -0700
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA09373
          for <freebsd-ports@FreeBSD.org>; Tue, 9 May 1995 03:29:53 -0700
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id DAA28355; Tue, 9 May 1995 03:29:49 -0700
Date: Tue, 9 May 1995 03:29:49 -0700
Message-Id: <199505091029.DAA28355@silvia.HIP.Berkeley.EDU>
To: wsantee@wsantee
CC: freebsd-ports@FreeBSD.org
In-reply-to: <199505090707.AAA00228@wsantee> (message from Wes Santee on Tue, 9 May 1995 00:07:50 -0700 (PDT))
Subject: Re: pdksh choading on exec command
From: asami@CS.Berkeley.EDU (Satoshi Asami | =?ISO-2022-JP?B?GyRCQHUbKEI=?= =?ISO-2022-JP?B?GyRCOCsbKEIgGyRCOC0bKEI=?=)
Sender: ports-owner@FreeBSD.org
Precedence: bulk

 * exec tput clear
 * 
 * Typing this in at the pdksh prompt, it logged me out of the system.

I know nothing about pdksh, but the reason why this logs you out is
because it's "exec", and the ksh executable is substituted with the
tput executable, which exits promptly after doing the "clear" command.
Try "exec csh", then "exit", and see where you end up with.

I'll leave the rest to ksh hackers. :)

Satoshi