From owner-freebsd-questions@FreeBSD.ORG Sun Aug 10 13:06:59 2003 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 84C5C37B401 for ; Sun, 10 Aug 2003 13:06:59 -0700 (PDT) Received: from munk.nu (213-152-51-194.dsl.eclipse.net.uk [213.152.51.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6182643FAF for ; Sun, 10 Aug 2003 13:06:56 -0700 (PDT) (envelope-from munk@munk.nu) Received: from munk by munk.nu with local (Exim 4.20) id 19lwSs-0009nR-CS for freebsd-questions@freebsd.org; Sun, 10 Aug 2003 21:06:54 +0100 Date: Sun, 10 Aug 2003 21:06:54 +0100 From: Jez Hancock To: freebsd-questions@freebsd.org Message-ID: <20030810200654.GA37421@users.munk.nu> Mail-Followup-To: freebsd-questions@freebsd.org References: <20030810155739.M51692@enabled.com> <20030810163614.GH76053@submonkey.net> <20030810164131.M87380@enabled.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030810164131.M87380@enabled.com> User-Agent: Mutt/1.4.1i Sender: User Munk Subject: Re: /usr/local/etc/rc.d files not running on reboot 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, 10 Aug 2003 20:06:59 -0000 On Sun, Aug 10, 2003 at 08:45:21AM -0800, admin wrote: > On Sun, 10 Aug 2003 17:36:14 +0100, Ceri Davies wrote > > On Sun, Aug 10, 2003 at 07:59:55AM -0800, admin wrote: > > > FreeBSD 4.8-STABLE > > > > > > My machine crashed last night and upon reboot not all the services that are > > > executable in the /usr/local/etc/rc.d ran. Any clues how I can find out why > > > this happened? > > > > A number of the files listed are not executable, and therefore won't > > get run. When this happens, the rc system usually prints a message > > "skipping foo.sh, not executable". > > > > Hi, > > okay cool - I understand that. > > but cucipop, for example never started but is executable. there is no message > claiming the skipping of cucipop: > > shell% grep skipping /var/log/messages > shell% I don't think you'll see the error messages from rc in the messages log - you'd have to watch the server console ttyv0 to view those error messages. > > > what else could be happening here? What happens when you run: /usr/local/etc/rc.d/cucipop.sh start ? -- Jez http://www.munk.nu/