From owner-freebsd-arch@FreeBSD.ORG Tue Jun 3 22:02:22 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF5BC37B405 for ; Tue, 3 Jun 2003 22:02:22 -0700 (PDT) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2A7F43FA3 for ; Tue, 3 Jun 2003 22:02:21 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-2ivfk3b.dialup.mindspring.com ([165.247.208.107] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19NQPV-0005qv-00; Tue, 03 Jun 2003 22:02:06 -0700 Message-ID: <3EDD7CFA.4795FB99@mindspring.com> Date: Tue, 03 Jun 2003 22:00:42 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Jeremy References: <20030602171942.GA87863@roark.gnf.org> <20030603080456.GA57773@cirb503493.alcatel.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a469078f9ef7624eb53b3580900cb48cfc667c3043c0873f7e350badd9bab72f9c350badd9bab72f9c cc: arch@freebsd.org cc: Matthew Dillon Subject: Re: Making a dynamically-linked root X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2003 05:02:23 -0000 Peter Jeremy wrote: > On Mon, Jun 02, 2003 at 02:25:43PM -0700, Matthew Dillon wrote: > > start!). Running certain daemon startups in the background might yield > > a significant overall improvement in startup times. > > This isn't a definite win. I know in the past it used to actually > slow things down: To take your example, having both sshd and sendmail > attempting to fault-in from disk in parallel will thrash both the disk > and cache far more than sshd and sendmail sequentially faulting in. A > very large number of daemons trying to start in parallel will also > stress the scheduler. The main problem we ran into with doing this on the InterJet was thatsome services started later would finish starting before earlier services on which they were dependent. It's not very good, for example, for sendmail to try to get its name that it's going to use in conversations with its peers from a DNS that's not up yet, or for it to try to log an error about that failure to a syslogd that's not up yet, or for cron to try to send a mail message about a job that's just completed, but sendmail isn't up, etc.. People try to pretend that the dependencies that exist are between programs, but they're actually between service providers and service consumers, and largely independent of the programs providing the services. On top of that, the dependencies tend to be both hard and soft, e.g. it's possible to continue to offer a degraded service, rather than failing outright, if some dependent services aren't there (e.g. you can log by IP address if DNS isn't up to provide reverse name mappings to look pretty in your logs, etc.). -- Terry