From owner-freebsd-ports@FreeBSD.ORG  Thu Mar 23 19:10:28 2006
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
X-Original-To: freebsd-ports@freebsd.org
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id BBEAD16A400
	for <freebsd-ports@freebsd.org>; Thu, 23 Mar 2006 19:10:28 +0000 (UTC)
	(envelope-from pauls@utdallas.edu)
Received: from smtp1.utdallas.edu (smtp1.utdallas.edu [129.110.10.12])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8180B43D45
	for <freebsd-ports@freebsd.org>; Thu, 23 Mar 2006 19:10:28 +0000 (GMT)
	(envelope-from pauls@utdallas.edu)
Received: from utd59514.utdallas.edu (utd59514.utdallas.edu [129.110.3.28])
	by smtp1.utdallas.edu (Postfix) with ESMTP id 2C232388EE3
	for <freebsd-ports@freebsd.org>; Thu, 23 Mar 2006 13:10:28 -0600 (CST)
Date: Thu, 23 Mar 2006 13:10:10 -0600
From: Paul Schmehl <pauls@utdallas.edu>
To: freebsd-ports@freebsd.org
Message-ID: <0EF5CD301A7EA4ABAE895ACD@utd59514.utdallas.edu>
X-Mailer: Mulberry/4.0.0b4 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: Startup at boot problem
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Mar 2006 19:10:28 -0000

I'm working on a new port that uses tcl scripting rather than compiled 
binaries.  The startup script works fine except at boot.  During the boot, 
I get this error message:
"exec: tclsh8.4: not found"

The script has the following in the "header" section:
# PROVIDE: sensor_agent
# REQUIRE: LOGIN tclsh8.4
# BEFORE: LOGIN
# KEYWORD: FreeBSD shutdown

Is there some other word I can use in REQUIRE that will allow tclsh8.4 to 
be found?

Paul Schmehl (pauls@utdallas.edu)
Adjunct Information Security Officer
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/