Lewis Thompson <[EMAIL PROTECTED]> wrote: > On Sun, Jun 20, 2004 at 03:01:54PM -0400, Chuck Swiger wrote: > > Lewis Thompson wrote: > > >I'm trying to create a port for a Python application that I want to > > >start from local/etc/rc.d. The command is this: > > > > > >/usr/bin/su freevo -c "/usr/local/bin/freevo -fs start" > /dev/null 2>&1 > > > > > > Unfortunately when I boot up I get a message about Python not being > > >configured/available at this time. > > > > 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?
I don't have much Python-fu, but is sure sounds like the script is failing becuase something it's dependent on hasn't started yet. Check to see what other scripts are in /usr/local/etc/rc.d (I'm guessing that's how you're firing it up on startup) and see if Python has some sort of startup script in there. If so, make sure your script executes afterwards (they're run alphabetically). If that doesn't help, you'll probably have to gather more details. The other suggestions about PATH and other environment are valid concerns as well. -- Bill Moran Potential Technologies http://www.potentialtech.com _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"