From owner-freebsd-rc@FreeBSD.ORG Thu Oct 25 19:32:44 2012 Return-Path: Delivered-To: freebsd-rc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 318C8429; Thu, 25 Oct 2012 19:32:44 +0000 (UTC) (envelope-from crees@FreeBSD.org) Received: from freefall.freebsd.org (freefall.FreeBSD.org [8.8.178.135]) by mx1.freebsd.org (Postfix) with ESMTP id 02D4B8FC14; Thu, 25 Oct 2012 19:32:44 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q9PJWh58097536; Thu, 25 Oct 2012 19:32:43 GMT (envelope-from crees@freefall.freebsd.org) Received: (from crees@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q9PJWhPk097532; Thu, 25 Oct 2012 19:32:43 GMT (envelope-from crees) Date: Thu, 25 Oct 2012 19:32:43 GMT Message-Id: <201210251932.q9PJWhPk097532@freefall.freebsd.org> To: eugene@donpac.ru, crees@FreeBSD.org, freebsd-rc@FreeBSD.org From: crees@FreeBSD.org Subject: Re: conf/105689: [ppp] [request] syslogd starts too late at boot X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Oct 2012 19:32:44 -0000 Synopsis: [ppp] [request] syslogd starts too late at boot State-Changed-From-To: open->feedback State-Changed-By: crees State-Changed-When: Thu Oct 25 19:32:43 UTC 2012 State-Changed-Why: I believe there's a chicken/egg problem here. What if syslogd was on a remote machine that ppp was required for? Personally I think this risk is greater than the benefit from adding REQUIRE: syslogd to ppp. http://www.freebsd.org/cgi/query-pr.cgi?pr=105689