Date: Sun, 26 Feb 2006 15:50:20 -0600 From: Paul Schmehl <pauls@utdallas.edu> To: Joacim Melin <listor@melin.org>, freebsd-questions@freebsd.org Subject: Re: Startup script Message-ID: <D97982D75B583801EB7CF0F6@Paul-Schmehls-Computer.local> In-Reply-To: <066085E5-2953-44ED-9C17-8B0FF8FC22FB@melin.org> References: <C1F18591-C716-4942-BD86-39C7BA56D816@melin.org> <17410.1177.855898.400422@jerusalem.litteratus.org> <066085E5-2953-44ED-9C17-8B0FF8FC22FB@melin.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--On February 26, 2006 9:54:45 PM +0100 Joacim Melin <listor@melin.org> wrote: > And if there isn't any /etc/rc.local I just create one and put stuff in > there? > No, no, no....when you install ports, their scripts are installed in /usr/local/etc/rc.d/. System daemons are installed in /etc/rc.d/. You should never have to write a startup script for a port you install. We maintainers are responsible for doing that. If a port doesn't install a daemon, there may not be a startup script. In that case, you can write one. Read man (8) rc.d and man (8) rc.subr for details. Rc.local is deprecated and seldom needs to be used (although it's still available.) After you install a port, go read the script in /usr/local/etc/rc.d. It will tell you what the options are that you can put into /etc/rc.conf. In most cases a simple portname_enable="YES" is all that's needed, but some will have flags that can be set or other options that you might want to use. (The same is true of /etc/rc.d scripts. E.g. /etc/rc.d/named.) Paul Schmehl (pauls@utdallas.edu) Adjunct Information Security Officer University of Texas at Dallas AVIEN Founding Member http://www.utdallas.edu/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D97982D75B583801EB7CF0F6>