You are not logged in.
Pages: 1
Here's my daemons line in the rc.conf:
DAEMONS=(syslog-ng net-profiles network firestarter netfs portmap fam dbus hal crond alsa sensors mysqld)
Are there any I can make start in the background or that are unnecessary? Also, what are netfs and crond?
Last edited by Gauvenator (2008-05-03 23:42:08)
Offline
Here is mine:
DAEMONS=(syslog-ng !network !netfs crond hal @alsa @net-profiles @fam @cpufreq @ntpd @mpd @sshd)
Offline
... Also, what are netfs and crond?
crond => Cron-Daemon (Link_to_Wikipedia)
netfs => Daemon needed to mount net-filesystems
"The mind can make a heaven out of hell or a hell out of heaven" -- John Milton
Offline
OK I've been toying with it and now it's like this:
DAEMONS=(syslog-ng net-profiles !network firestarter !netfs portmap fam dbus hal crond @mysqld @alsa @sensors)
It doesn't make a difference over the same thing without the ! and @. Both boot 26s according to bootchart.
Anything else I should try? Can I @crond safely?
Offline
Backgrounding crond, fam, dbus and hal got it down to 24s. The slowest part is net-profiles....it takes several seconds to turn the wireless on.
Offline
Except from syslog-ng i have all my daemons in background...no problems at all.Never.
Am I Lucky?
Offline
try @syslog-ng @net-profiles !network @firestarter !netfs @portmap @fam @hal @crond @mysqld @alsa @sensors
hal starts dbus if its not started and i dont think theres a problem with backgrounding all the daemons
There shouldn't be any reason to learn more editor types than emacs or vi -- mg (1)
[You learn that sarcasm does not often work well in international forums. That is why we avoid it. -- ewaller (arch linux forum moderator)
Offline
You can use gamin instead of fam.
Just remove fam from your system and install gamin. It's not needed to put gamin to the daemons list, just install it and you are done.
Last edited by SiD (2008-05-04 11:32:01)
Offline
hal starts dbus if its not started and i dont think theres a problem with backgrounding all the daemons
I'm not sure about this. But I think it's not a good thing to background daemons of which other daemons depend. Like backgrounding network, while others need it to start correctly. You can't just assume that the backgrounded daemon will be up and running until the other daemon starts.
But again, I'm not sure about this.
Anyway, what's the difference of having a system that boots in 30 or 20 seconds when you're going to use it for hours?
Offline
dolby wrote:hal starts dbus if its not started and i dont think theres a problem with backgrounding all the daemons
I'm not sure about this. But I think it's not a good thing to background daemons of which other daemons depend. Like backgrounding network, while others need it to start correctly. You can't just assume that the backgrounded daemon will be up and running until the other daemon starts.
But again, I'm not sure about this.
Anyway, what's the difference of having a system that boots in 30 or 20 seconds when you're going to use it for hours?
Yes that's what I was thinking too. A daemon could depend on another being running.
Well I'm happy atm, but just for the hell of it I'm going to see how quick it is without net-profiles
Offline
hehe 18s without net-profiles and firestarter. Too bad I needs t3h 1nt3rw3bz
Well, 24s is satisfactory.
Offline
Pages: 1