Need all these modules in rc.conf? And which daemons to background?

chrispoole · 2009-03-27 15:41:40

Hi,

I have these modules listed in rc.conf:

snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore !snd-pcsp

(I've grabbed suggestions from an EEE article or two in the wiki, and the beginners' guide (I have an EEE 1000H).

Surely not all of these are required; can someone point me towards seeing which ones are required, and which ones are just slowing my boot time?

Also, I have these daemons:

syslog-ng !network dhclient netfs crond alsa acpid hal !dhcdbd !networkmanager wicd fam sshd cups laptop-mode stbd ntpd

I'm not sure which ones I can background. Can anyone help with this, or point me to a page that shows dependencies? (I've looked, but can't find an answer.)

Thanks

byte · 2009-03-27 15:44:20

For MODULES: get rid of everything, except !snd-pcsp

dannytatom · 2009-03-27 15:45:09

I'm guessing it differs per computer, but my module list has always been empty and it works just fine.

brisbin33 · 2009-03-27 15:47:38

personally, i background everything except syslog-ng and network. because i want logging and network up before anything else starts, after that i don't care what happens in what order.

in your case though i would let syslog-ng, hal, and wcid (b/c wcid depends on hal) start then background the rest as that's the equivalent of my approach (i think); i don't use wireless so i'll step aside if someone's got a better best-practice.

as for modules, there's an lsmod command that i can't remember right now to tell you which one's you're actively using. generally speaking MOD_AUTOLOAD="yes" should take care of it, then just use MODULES array to blacklist things like !pcspkr

Inxsible · 2009-03-27 15:50:28

brisbin33 wrote:

personally, i background everything except syslog-ng and network.

+1

I have even backgrounded (is that a word?) hal -- as long as everything after hal is backgrounded, hal should start up before the rest. I haven't had any toruble. The only thing that is not backgrounded in my DAEMONS array is syslog-ng

My MODULES array only has (!iTCO_wdt !shlc) -- i have to disable iTCO_wdt, so that udev can actually finish processing - this started happening since about 3 kernel updates prior, haven't taken it out since -- although I should see if the latest kernel fixed it. shlc is the module for my dial-up -- which I never use.

By the way, if you have hal in your DAEMONS array , you do not need to add acpid because hal will automatically start it up.

Last edited by Inxsible (2009-03-27 15:53:22)

thisperishedmin · 2009-03-27 16:30:06

hmm...I'm going to fire out my own noobish question (not to threadjack!) but...I thought backgrounding had the task load at the same time as everything else, after all non background tasks...

for that reason I'm kind of confused by the suggestions but I'm sure I'm just approaching with the wrong thought pattern...

could someone differentiate / explain exactly whats going on or exactly what backgrounding actually does???

thanks!!

brisbin33 · 2009-03-27 16:44:02

each daemon will be loaded in sequence as per DAEMONS=(). putting the @ for background simply means "DONT wait for the guy before you to finish before you start" so each process is started in sequence but hal won't have to finish loading before sshd is started.

DAEMONS=(... hal ... sshd ...) is like:
> hal && sshd

where as

DAEMONS=( ... @hal ... sshd ...) is like:
> hal &
> sshd

thisperishedmin · 2009-03-27 17:12:22

Ah okay! thank you.

I knew that, but just confused myself by overthinking I suppose. your wording is much simpler than how I was trying to envision it. haha, gracias!

my0pic · 2009-03-27 22:18:31

brisbin33 wrote:

as for modules, there's an lsmod command that i can't remember right now to tell you which one's you're actively using. generally speaking MOD_AUTOLOAD="yes" should take care of it, then just use MODULES array to blacklist things like !pcspkr

# hwdetect --show-modules-order

This will show you all modules loaded in the order they where loaded. You can specify these on the modules line but as brisbin33 suggested, MOD_AUTOLOAD="yes" plus your blacklisted modules is enough.

adamlau · 2009-03-28 01:18:22

Info from my current box:

MODULES=(e100 fuse loop)
DAEMONS=(@hal @network @cups @alsa)

droog · 2009-03-28 04:01:55

Nevermind just saw this was for eee.

Last edited by droog (2009-03-28 04:10:18)

cdwillis · 2009-03-28 06:07:56

adamlau wrote:

Info from my current box:

MODULES=(e100 fuse loop)
DAEMONS=(@hal @network @cups @alsa)

Isn't it a bad idea not to have syslog-ng in the daemons array?

SkonesMickLoud · 2009-03-28 07:13:52

cdwillis wrote:

adamlau wrote:
Info from my current box:
MODULES=(e100 fuse loop)
DAEMONS=(@hal @network @cups @alsa)
Isn't it a bad idea not to have syslog-ng in the daemons array?

Not everyone cares about logs.

bernarcher · 2009-03-28 08:42:18

adamlau wrote:

Info from my current box:

MODULES=(e100 fuse loop)
DAEMONS=(@hal @network @cups @alsa)

Is it a good idea to background hal?
There may be issues because hal (and dbus btw) ought to be initialized before some other stuff can be run, I always thought.

vacant · 2009-03-28 09:09:20

I run my laptop wirelessly with wicd, card uses "wl" module. I deleted "network" from my daemons long ago.

MODULES=(powernow-k8 cpufreq_ondemand cpufreq_powersave fuse sky2 wl)
DAEMONS=(syslog-ng hal @wicd @dnsmasq @sensors @ntpdate @crond @cpufreq @laptop-mode)

Arch Linux

#1 2009-03-27 15:41:40

Need all these modules in rc.conf? And which daemons to background?

#2 2009-03-27 15:44:20

Re: Need all these modules in rc.conf? And which daemons to background?

#3 2009-03-27 15:45:09

Re: Need all these modules in rc.conf? And which daemons to background?

#4 2009-03-27 15:47:38

Re: Need all these modules in rc.conf? And which daemons to background?

#5 2009-03-27 15:50:28

Re: Need all these modules in rc.conf? And which daemons to background?

#6 2009-03-27 16:30:06

Re: Need all these modules in rc.conf? And which daemons to background?

#7 2009-03-27 16:44:02

Re: Need all these modules in rc.conf? And which daemons to background?

#8 2009-03-27 17:12:22

Re: Need all these modules in rc.conf? And which daemons to background?

#9 2009-03-27 22:18:31

Re: Need all these modules in rc.conf? And which daemons to background?

#10 2009-03-28 01:18:22

Re: Need all these modules in rc.conf? And which daemons to background?

#11 2009-03-28 04:01:55

Re: Need all these modules in rc.conf? And which daemons to background?

#12 2009-03-28 06:07:56

Re: Need all these modules in rc.conf? And which daemons to background?

#13 2009-03-28 07:13:52

Re: Need all these modules in rc.conf? And which daemons to background?

#14 2009-03-28 08:42:18

Re: Need all these modules in rc.conf? And which daemons to background?

#15 2009-03-28 09:09:20

Re: Need all these modules in rc.conf? And which daemons to background?

Board footer