[Solved]Lengthy network init during boot

zacariaz · 2012-01-18 08:27:55

While I wait for an answer to a more important question, I thought that I'd just pose this one.

The thing is that I've installed Arch on and SSD (why you ask? because I could ) and that's all well and good, but the 30 second halt during boot, for the purpose of setting up the networks (or whatever it does), I could certainly be without, thus I ask you all what, if anything, I can do about it.

Best regards

Last edited by zacariaz (2012-01-18 08:54:39)

karol · 2012-01-18 08:35:37

You can background the daemons in rc.conf by prefixing it with '@':

DAEMONS=(... @network ...)

zacariaz · 2012-01-18 08:38:50

karol wrote:

You can background the daemons in rc.conf by prefixing it with '@':
DAEMONS=(... @network ...)

That is very cool, not least Because it's easy to remember.

But is it save to do? Might I experience problems or will the result be exactly the same?

Can this be done with any other deamon without trouble?

Best regards.

karol · 2012-01-18 08:41:06

It's a standard way of speeding up your boot, I have been doing it for years w/o any problems.
Just don't expect the network to be up as soon as your computer finishes booting, it may take a couple seconds more for the network to "catch up".

Edit: Sure, you can do it with other daemons, I have

DAEMONS=(syslog-ng dbus @acpid @gpm @network @crond @alsa @atd @vnstat)

I'm not backgrounding the first two, because I want to have things logged (syslog-ng) and dbus is needed for the other stuff to work, so I want to make sure it gets loaded first.

Last edited by karol (2012-01-18 08:45:01)

zacariaz · 2012-01-18 08:46:58

karol wrote:

It's a standard way of speeding up your boot, I have been doing it for years w/o any problems.
Just don't expect the network to be up as soon as your computer finishes booting, it may take a couple seconds more for the network to "catch up".

Well, before the xserver is up and running and such, it will probably be over with.

Anyway, just to make sure...

DAEMONS=(@syslog-ng @network @crond @dbus)

Would be completely safe? How about changing the order?

Well, I guess it's fine for now, but an instant boot is all noob geeks dream

karol · 2012-01-18 08:51:50

I think dbus should be in the front.
I've never actually checked what's the difference between backgrounded and straight syslog but if I'm correct, if something goes wrong, it might not get logged and you will be in the dark wrt to what exactly went wrong.

zacariaz · 2012-01-18 08:53:01

Ok, that settles it. Thanks a lot.

Arch Linux

#1 2012-01-18 08:27:55

[Solved]Lengthy network init during boot

#2 2012-01-18 08:35:37

Re: [Solved]Lengthy network init during boot

#3 2012-01-18 08:38:50

Re: [Solved]Lengthy network init during boot

#4 2012-01-18 08:41:06

Re: [Solved]Lengthy network init during boot

#5 2012-01-18 08:46:58

Re: [Solved]Lengthy network init during boot

#6 2012-01-18 08:51:50

Re: [Solved]Lengthy network init during boot

#7 2012-01-18 08:53:01

Re: [Solved]Lengthy network init during boot

Board footer