/usr/local/etc/rc.d files not running on reboot

[Jez Hancock]

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/