Arch Linux

toorlv

Member

Registered: 2009-11-01

Posts: 65

Proper positioning of daemons (rc.conf)

DAEMONS=(!syslog-ng @cpufreq @crond hal fam @alsa !network @dhcdbd @networkmanager @gdm)

How to speed up boot process? How to proper position this daemons?

flamelab

Member

From: Athens, Hellas (Greece)

Registered: 2007-12-26

Posts: 2,160

Re: Proper positioning of daemons (rc.conf)

Move hal after syslog-ng, add a "@"before fam, move @alsa to the end before @gdm.

jithin1987

Member

From: Bangalore

Registered: 2009-09-12

Posts: 182

Re: Proper positioning of daemons (rc.conf)

This is from my rc.conf
DAEMONS=(syslog-ng cpufreq laptop-mode dbus hal !network networkmanager
avahi-daemon avahi-dnsconfd alsa !cdemud cups kdm)

Which ones should I add @ . Then how will I know if it failed or not ?

---

Thanks
Jithin

skottish

Forum Fellow

From: Here

Registered: 2006-06-16

Posts: 7,942

Re: Proper positioning of daemons (rc.conf)

This is from my rc.conf
DAEMONS=(syslog-ng cpufreq laptop-mode dbus hal !network networkmanager
avahi-daemon avahi-dnsconfd alsa !cdemud cups kdm)

Which ones should I add @ ...

If your happy with your boot time, then backgrounding is unnecessary.

Then how will I know if it failed or not ?

Not trying to be a smart ass, but when you discover that they're not working. With that being said, remove dbus because hal starts it automatically. Other than that and without knowing your system, backgrounding cpufreq, laptop-mode, networkmanager, both avahi, alsa, and cups, could work out alright.

Liquid

Member

Registered: 2009-10-27

Posts: 13

Re: Proper positioning of daemons (rc.conf)

What does ! and @ symbols mean ? Are they necessary ?

mcsaba77

Member

From: Ho Chi Minh City, Vietnam

Registered: 2009-09-30

Posts: 52

Re: Proper positioning of daemons (rc.conf)

The answer is right above the DAEMONS array in rc.conf

# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng hal @cpufreq @crond @wicd @pulseaudio @cups)

It's worthwile to read the comments in config files sometimes

dcc24

Member

Registered: 2009-10-31

Posts: 732

Re: Proper positioning of daemons (rc.conf)

Here's my daemons array, it might be useful.

DAEMONS=(syslog-ng !network polkitparser hal networkmanager netfs @crond !rpcbind @fam @alsa @cpufreq @sensors !bluetooth @sshd @slim)

---

It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)

My AUR packages

japetto

Member

From: Chicago, IL US

Registered: 2006-07-02

Posts: 183

Re: Proper positioning of daemons (rc.conf)

http://wiki.archlinux.org/index.php/Rc.conf
http://wiki.archlinux.org/index.php/Beg … .2Frc.conf

Useful and recommended info in both of those links.

Last edited by japetto (2009-11-07 16:07:14)

skottish

Forum Fellow

From: Here

Registered: 2006-06-16

Posts: 7,942

Re: Proper positioning of daemons (rc.conf)

I'm curious why people are backgrounding their login manager. Seems kind of pointless since you're waiting for it.

jithin1987

Member

From: Bangalore

Registered: 2009-09-12

Posts: 182

Re: Proper positioning of daemons (rc.conf)

dbus needs to be added before hal because if not during restart/shutdown networkmanger fails to close.

---

Thanks
Jithin

jithin1987

Member

From: Bangalore

Registered: 2009-09-12

Posts: 182

Re: Proper positioning of daemons (rc.conf)

I see a lot of people using fam daemon. I heard gamin is better. Is there any particular reason fam is used?

---

Thanks
Jithin

dalingrin

Member

Registered: 2009-03-18

Posts: 128

Re: Proper positioning of daemons (rc.conf)

dbus needs to be added before hal because if not during restart/shutdown networkmanger fails to close.

As far as I know, dbus is started by hal. There is no need to start them separately.

skottish

Forum Fellow

From: Here

Registered: 2006-06-16

Posts: 7,942

Re: Proper positioning of daemons (rc.conf)

dbus needs to be added before hal because if not during restart/shutdown networkmanger fails to close.

As far as I know, dbus is started by hal. There is no need to start them separately.

This is true. So, if both dbus and hal need to be explicitly started then there's something wrong with the system.