You are not logged in.
Today I had waited to see how long it will take my system to boot and then have realized that it took too long to run "Network". Is this something usual?
Offline
Same here since the last update of dhcpcd
Offline
If you are just impatient, then simply background the network daemon in rc.conf.
Are you experiencing connectivity issues?
Offline
It takes about 5-10 seconds to start Network for me. I just backgrounded it in rc.conf, and now I don't even notice.
[ lamy + pilot ] [ arch64 | wmii ] [ ati + amd ]
Offline
It's the easiest thing to add a "@" sign I wonder if it's an usual problem, though maybe its not a problem.
edit: it doesnt seem to be a problem, so thanks anyway.
Last edited by Yunus Emre (2008-10-29 13:21:21)
Offline
It is a problem for me. I use Samba network filesystems in /etc/fstab. If I set the network daemon to be started in background, sometimes at shutdown network filesystems are umounted after network daemon is stopped. Then it takes a long time, waiting for a timeout because network is down. So the network daemon is the only I have not to start in background.
Offline
you guys reboot?
Offline
@fuscia,
don't you reboot?
Offline
Sure, I reboot for kernel upgrades and whenever I get the itch for some Battlefield or Counter-Strike. Neither of them happen too often, but I do reboot occasionally.
[ lamy + pilot ] [ arch64 | wmii ] [ ati + amd ]
Offline
@fuscia,
don't you reboot?
occassionally, but just to keep my skills up.
Offline
That's interesting, am I doing wrong? I often shutdown my pc since it's consuming electric.
Offline
That's interesting, am I doing wrong?
I often shutdown my pc since it's consuming electric.
just suspend/hibernate it
Offline