News for hackers. Stuff that matters.

A comment on Why systemd?. Parent comment

Re:Why systemd? by chousuke on Tuesday September 23, 2014 @05:29AM (#8354635)
My FreeBSD system has a 30-second timeout during which the entire boot process is halted because it waits for a default route to the internet... which it won't get, because I haven't configured one.

It's pretty dumb, and not enough of a problem for me that I'd figure out how to work around it, but it's a pretty good example.

[ Parent | on HN ]
Re:Why systemd? by allegory on Tuesday September 23, 2014 @06:38AM (#8354746)
Just set in rc.conf:

   defaultrouter="NO"
It shouldn't hang.
[ Parent | on HN ]
Re:Why systemd? by ash on Tuesday September 23, 2014 @05:49AM (#8354674)
I don't think this 30-second timeout is a bug in FreeBSD or in rc. You may want your server to wait for the network to become available. Ubuntu Server has the same "waiting for network" timeout:

http://askubuntu.com/questions/63456/waiting-for-network-con...

[ Parent | on HN ]
Re:Why systemd? by vidarh on Tuesday September 23, 2014 @08:12AM (#8354952)
But the only reason this is necessary is when the boot system isn't smart enough to start whatever can safely be started through proper dependencies.

My experience is that a substantial amount of time is wasted weeding out undesired timeouts in startup scripts, because they lead to increasing downtime.

[ Parent | on HN ]