/usr/local/etc/rc.d/*.sh not working?
Vivek Khera
vivek at khera.org
Tue Jun 14 15:22:09 GMT 2005
On Jun 14, 2005, at 11:10 AM, 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.
>
but his scripts don't use rc-ng, so this is pointless.
they should just work if they end in .sh and are executable.
> 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
>>
>>
>>
>
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-
> unsubscribe at freebsd.org"
>
Vivek Khera, Ph.D.
+1-301-869-4449 x806
More information about the freebsd-stable
mailing list