You are not logged in.
Pages: 1
From what I understand, selective editing of the DAEMONS line of rc.conf, including prefixing certain daemons with @, can significantly reduce boot time. I read a couple posts, as well as the wiki, searching for a solid answer, but the best I found was "which services to start background depends on your needs" which is a bit obvious. In any case, here's my current line:
DAEMONS=(syslog-ng !network netfs crond hal alsa hplip cups dhcdbd networkmanager laptop-mode gdm)
I'm sure it's a mess, as I've just slapped daemons on to fix problems, enable wireless, etc. so far.
If it's at all useful, this is a laptop that I commonly use as a workstation and with wireless.
Last edited by ArchPad (2007-06-13 14:34:41)
Offline
From what I understand, selective editing of the DAEMONS line of rc.conf, including prefixing certain daemons with @, can significantly reduce boot time. I read a couple posts, as well as the wiki, searching for a solid answer, but the best I found was "which services to start background depends on your needs" which is a bit obvious. In any case, here's my current line:
DAEMONS=(syslog-ng !network netfs crond hal alsa hplip cups dhcdbd networkmanager laptop-mode gdm)
I'm sure it's a mess, as I've just slapped daemons on to fix problems, enable wireless, etc. so far.
If it's at all useful, this is a laptop that I commonly use as a workstation and with wireless.
Put an @ before all of them, it shouldn't cause problems but will cause a tremendous improvement in boot time.
And did you disable network on purpose?
Last edited by Ramses de Norre (2007-06-13 14:41:52)
Offline
ArchPad wrote:From what I understand, selective editing of the DAEMONS line of rc.conf, including prefixing certain daemons with @, can significantly reduce boot time. I read a couple posts, as well as the wiki, searching for a solid answer, but the best I found was "which services to start background depends on your needs" which is a bit obvious. In any case, here's my current line:
DAEMONS=(syslog-ng !network netfs crond hal alsa hplip cups dhcdbd networkmanager laptop-mode gdm)
I'm sure it's a mess, as I've just slapped daemons on to fix problems, enable wireless, etc. so far.
If it's at all useful, this is a laptop that I commonly use as a workstation and with wireless.
Put an @ before all of them, it shouldn't cause problems but will cause a tremendous improvement in boot time.
And did you disable network on purpose?
I did because I'm letting networkmanager handle my networking.
Adding @ before all of them resulted in no faster boot time. After UDev, it whipped through the events, but I was waiting at a terminal login for ten seconds or so before GDM started.
Last edited by ArchPad (2007-06-13 15:01:11)
Offline
Put gdm in front of all the others...
My victim you are meant to be
No, you cannot hide nor flee
You know what I'm looking for
Pleasure your torture, I will endure...
Offline
Also, when I did added @ before each, my gnome-network-manager and gnome-power-manager applets never showed up, leading me to believe that some daemons never started...
Offline
From what I understand, selective editing of the DAEMONS line of rc.conf, including prefixing certain daemons with @, can significantly reduce boot time. I read a couple posts, as well as the wiki, searching for a solid answer, but the best I found was "which services to start background depends on your needs" which is a bit obvious. In any case, here's my current line:
DAEMONS=(syslog-ng !network netfs crond hal alsa hplip cups dhcdbd networkmanager laptop-mode gdm)
I'm sure it's a mess, as I've just slapped daemons on to fix problems, enable wireless, etc. so far.
If it's at all useful, this is a laptop that I commonly use as a workstation and with wireless.
Certain daemons likely depend on other things already having started before they initiate their startup, so you want to leave some alone. Here is my array, and although different than yours, notice how I leave quite a few things un-backgrounded due to dependencies and lump all the backgrounded ones at the end:
DAEMONS=(syslog-ng network iptables portmap @fcron @hal @sensors @knockd @netfs @sshd @ntpd @alsa @cups)
This would lead me to believe something like this would work for you (and WHY do you have network disabled?):
DAEMONS=(syslog-ng network hplip @crond @hal @netfs @alsa @cups @dhcdbd @networkmanager @laptop-mode @gdm)
Offline
ArchPad wrote:From what I understand, selective editing of the DAEMONS line of rc.conf, including prefixing certain daemons with @, can significantly reduce boot time. I read a couple posts, as well as the wiki, searching for a solid answer, but the best I found was "which services to start background depends on your needs" which is a bit obvious. In any case, here's my current line:
DAEMONS=(syslog-ng !network netfs crond hal alsa hplip cups dhcdbd networkmanager laptop-mode gdm)
I'm sure it's a mess, as I've just slapped daemons on to fix problems, enable wireless, etc. so far.
If it's at all useful, this is a laptop that I commonly use as a workstation and with wireless.
Certain daemons likely depend on other things already having started before they initiate their startup, so you want to leave some alone. Here is my array, and although different than yours, notice how I leave quite a few things un-backgrounded due to dependencies and lump all the backgrounded ones at the end:
DAEMONS=(syslog-ng network iptables portmap @fcron @hal @sensors @knockd @netfs @sshd @ntpd @alsa @cups)
This would lead me to believe something like this would work for you (and WHY do you have network disabled?):
DAEMONS=(syslog-ng network hplip @crond @hal @netfs @alsa @cups @dhcdbd @networkmanager @laptop-mode @gdm)
I have syslog-ng and network backgrounded too and that works perfect.
Offline
I have network turned off because I listened to this: http://wiki.archlinux.org/index.php/Networkmanager
My network works fine without it.
Offline
I have all my daemons backgrounded and everything works fine. About 20 seconds to boot and login to Gnome :-)
"The hardest thing is rendering a moment moving to fast to endure"
Offline
Did you try this tweak?
/etc/rc.sysinit
add a '&' to the end of this line:
/sbin/modprobe $mod
so that it reads
/sbin/modprobe $mod &
Supposed to background module loading, may help a bit.
Offline
Pages: 1