Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 14 Jun 2005 16:21:10 +0100
From:      "Peter Cranmer" <peterj.cranmer@virgin.net>
To:        "Michael W. Lucas" <mwlucas@blackhelicopters.org>
Cc:        stable@freebsd.org
Subject:   Re: /usr/local/etc/rc.d/*.sh not working?
Message-ID:  <023e01c570f4$b78d7780$0100a8c0@peter>
References:  <20050614150240.GA62949@bewilderbeast.blackhelicopters.org><42AEF361.2010405@t-hosting.hu> <20050614151939.GA63065@bewilderbeast.blackhelicopters.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Put them all in the same directory and write a quick script to loop through 
the dir (make sure the directory's secure...).  Then you could just add that 
script to /etc/rc.conf?

peter

----- Original Message ----- 
From: "Michael W. Lucas" <mwlucas@blackhelicopters.org>
To: "K?vesd?n G?bor" <gabor.kovesdan@t-hosting.hu>
Cc: <stable@freebsd.org>
Sent: Tuesday, June 14, 2005 4:19 PM
Subject: Re: /usr/local/etc/rc.d/*.sh not working?


> That works fine for ports, but what about truly local custom scripts?
>
> For example, I have a server with about 400 separate MRTG daemons on
> it.  (Yes, they must be separate, for administrative rather than
> technical reasons.)  Each daemon has a custom script.  These aren't
> ports, and they have no rcNG infrastructure.
>
> They used to work fine.  Now they don't.  Obviously something has
> changed.
>
> I'd like to have just a plain old /usr/local/etc/rc.d/*.sh file get
> executed on boot, like it used to be, but if I have to change the
> scripts I will.
>
> On Tue, Jun 14, 2005 at 05:10:25PM +0200, K?vesd?n G?bor wrote:
>> For scripts in /usr/local/etc/rc.d You should add an entry to 
>> /etc/rc.conf.
>> For example, if You script is somedaemon.sh, then add
>> somedaemon_enable='YES' to /etc/rc.conf and it will run at the next boot.
>>
>> Cheers,
>>
>> G?bor K?vesd?n
>>
>> Michael W. Lucas wrote:
>>
>> >I'm certain this is documented somewhere, but danged if I can find it.
>> >
>> >I have a whole variety of custom scripts in /usr/local/etc/rc.d.  For
>> >years now, simply giving them a name ending in .sh and making them
>> >executable has been sufficient to make them start on boot.
>> >
>> >On 5.x, it's not.  And now, having upgraded to 4.11-s on some older
>> >boxes and running portupgrade -a, it's not.
>> >
>> >Obviously these scripts need something else.  There's no fancy rcNG
>> >infrastructure in them; is rcNG a requirement for startup scripts now?
>> >Any pointers on where I can find the right documentation?
>> >
>> >Thanks,
>> >
>> >==ml
>> >
>> >
>> >
>
> -- 
> Michael W. Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org
> http://www.BlackHelicopters.org/~mwlucas/
>
> "The cloak of anonymity protects me from the nuisance of caring." -Non 
> Sequitur
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?023e01c570f4$b78d7780$0100a8c0>