From owner-freebsd-current  Fri Feb 19  8:44:14 1999
Delivered-To: freebsd-current@freebsd.org
Received: from misha.cisco.com (misha.cisco.com [171.69.206.50])
	by hub.freebsd.org (Postfix) with ESMTP id 24FDA119CC
	for <current@freebsd.org>; Fri, 19 Feb 1999 08:44:01 -0800 (PST)
	(envelope-from mi@misha.cisco.com)
Received: (from mi@localhost)
	by misha.cisco.com (8.9.1/8.9.1) id LAA08791
	for current@freebsd.org; Fri, 19 Feb 1999 11:44:00 -0500 (EST)
	(envelope-from mi)
From: Mikhail Teterin <mi@misha.cisco.com>
Message-Id: <199902191644.LAA08791@misha.cisco.com>
Subject: sh(1) -- exec vs. fork
To: current@freebsd.org
Date: Fri, 19 Feb 1999 11:43:59 -0500 (EST)
Reply-To: mi@aldan.algebra.com
X-Mailer: ELM [version 2.4ME+ PL52 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I just finished going through a couple of crontabs prepending the
command-lines with ``exec'', when it hit me.

Can shell itself recognize, there will be no more commands and just
proceed to exec without forking? What would this break?

This should never, of course, happen in interactive mode...

The shell's source requires studying, but, may be, a knowledgeable
person can answer right away?

	-mi


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message