You are not logged in.
When I change both MODULES and DAEMONS in rc.conf (as root of course) do I have to to type/run a specific command that will enable/disable certain functions in the kernell, or those lines exist to enable/disable on-the-fly specific directives of the kernell?
as examble the acpid after the
# pacman -S acpid
I include the appropriate command in the deamons
then?
if I blacklist the acpid in deamons then do I need to run a specific command?
Last edited by trotos (2008-06-06 16:06:21)
Offline
i dont use acpid, but all your daemons you can start and stop by doing as root
/etc/rc.d/acpid start
/etc/rc.d/acpid stop
Offline
The modules and daemons entries in rc.conf really only apply when you're starting up or shutting down - the MODULES line says "load or blacklist these modules at startup" and the DAEMONS line says "load or blacklist these daemons at startup"
If you want to actually START the services while the machine is still running, or load the modules, you have to do
/etc/rc.d/service start
or
modprobe module
Offline
i win your post was alot more informative though.
Offline
hmmmmmm...everyday one man learns something new...
I knew about the
/etc/rc.d/service start
but what has to do with the kernell?
maybe nothing if i understand correctly, so no need to do everytime a compiling(if I ever had done one!!!???
instead it just call specific actions during boot,
another thing I do not understand from the wikis is the difference between MODULES and DAEMONS and how do I find out the best order for them, and the ones that should be used with the @, is there any rule of the thumb?
Last edited by trotos (2008-06-06 16:07:30)
Offline
modules and daemons are pretty standard faire in the Linux world. You could easily google them and find the difference, but since I'm feeling kind I'll explain it here.
Modules: These are kernel "drivers" essentially - they plug in to the kernel and tell it how to run hardware, for example
Daemons: These are applications that run in the background and provide some service - syslog-ng handles the creation of system logfiles in /var/log, mpd is a music playing daemon, etc...
As for ordering daemons, that's all based on dependencies. If something depends on the network being up, it should come after the network daemon, for example. For backgrounding them (pre-pending @), again that's up to you. It only really affects boot speed - I have some of the "less-critical" daemons backgrounded, like archstats, mpd, mediatomb, and a few others I forget right now.
Offline
@Cerebral:
You can speed up your boot by removing the archstats daemon. Archstats is dead. http://bugs.archlinux.org/task/9608
Offline