From owner-freebsd-questions@FreeBSD.ORG Sun Jun 20 19:56:59 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C015516A4CE for ; Sun, 20 Jun 2004 19:56:59 +0000 (GMT) Received: from out002.verizon.net (out002pub.verizon.net [206.46.170.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DEB143D1F for ; Sun, 20 Jun 2004 19:56:59 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.3] ([68.161.84.3]) by out002.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040620195658.OEXE9273.out002.verizon.net@[192.168.1.3]>; Sun, 20 Jun 2004 14:56:58 -0500 Message-ID: <40D5EBFB.5020106@mac.com> Date: Sun, 20 Jun 2004 15:56:43 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040608 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Lewis Thompson References: <20040620175144.GA68736@fajita.org> <40D5DF22.5020609@mac.com> <20040620191400.GA70741@fajita.org> In-Reply-To: <20040620191400.GA70741@fajita.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out002.verizon.net from [68.161.84.3] at Sun, 20 Jun 2004 14:56:57 -0500 cc: FreeBSD-questions Subject: Re: Python application in rc.d. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jun 2004 19:56:59 -0000 Lewis Thompson wrote: [ ... ] >>Does the script set $PATH to include the location where python is? If you >>don't list /usr/local/bin explicitly, this may be the problem... > > No, PATH doesn't get set but if I run it as /usr/local/bin/freevo.sh start > from a login shell (i.e. after the system has booted) it works fine. I > might be getting confused but I think this indicates the script is good > and it's a start-up problem. Is this just wrong? No, you should not assume that running the command from an interactive shell is the same environment that a RC startup script or a cron job runs under. Adding an "echo $PATH" somewhere would probably give you more information, but without a more specific error message, I'll repeat my guess. [ Without seeing the exact error message, asking us what's really going on involves jedi mind tricks! :-) ] -- -Chuck