On Wednesday, May 16, 2012 02:15:19 PM Neil Bothwick wrote: > On Wed, 16 May 2012 09:40:26 +0100, Ignas Anikevicius wrote: > > I want to do this, so that I do not have to wait while non-crucial > > services are being started (e.g. fcron, bitlbee, ntpd to name a few). > > Maybe it is possible to somehow prioritize the initscripts? > > Yes it is. The initscripts themselves have such a mechanism, using the > before and after statements, for example making sure that network > services are started after the network is brought up. You can add your > own rules to the daemons' config files in /etc/conf.d or to /etc/rc.conf. > > To have bitlbee start after xdm either add > > rc_after="xdm" > > to /etc/conf.d/bitlbee or put > > rc_bitlbee_after="xdm" > > in /etc/rc.conf. Both have the same effect, it depends on whether you > want to put all these settings together or in the individual services' > config files.
Putting them in /etc/rc.conf makes it simpler to maintain the init-scripts when updating packages. I used to put these things in the init-scripts and occasionally forgot about some of these during an update. -- Joost
