From owner-freebsd-questions Sat Jun 22 21: 7:13 2002 Delivered-To: freebsd-questions@freebsd.org Received: from skytrackercanada.com (cust29.209.188.66.dsl.accessv.com [209.188.66.29]) by hub.freebsd.org (Postfix) with ESMTP id 16B4D37B400 for ; Sat, 22 Jun 2002 21:07:10 -0700 (PDT) Received: (from david@localhost) by skytrackercanada.com (8.12.3/8.12.3) id g5N474ls012070 for questions@freebsd.org; Sun, 23 Jun 2002 00:07:04 -0400 (EDT) (envelope-from david) Date: Sun, 23 Jun 2002 00:07:04 -0400 From: David Banning To: questions@freebsd.org Subject: startup script question Message-ID: <20020623000704.A12064@skytrackercanada.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I am having a problem that some of my startup scripts are not firing up on boot. Specifically, adzapper.sh and zope.sh. They will start OK if I wait until the machine has finished it's boot, and then start them with eg. "sh /usr/local/etc/rc.d/zope.sh start" I figure that the problem comes in with the order that the scripts execute. Maybe the machine is busy during boot and does not yet have the resources to run adzapper and zope? Any ideas? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message