From owner-freebsd-questions@freebsd.org Sun Aug 26 17:31:21 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AD420107C687 for ; Sun, 26 Aug 2018 17:31:21 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3CC2D89114 for ; Sun, 26 Aug 2018 17:31:21 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wr1-x430.google.com with SMTP id j26-v6so11521604wre.2 for ; Sun, 26 Aug 2018 10:31:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=/1nRfrD5Cj6rT9iuUiMRdy0/0EW40YUdzXgbELbj4LA=; b=qylYbaO28UCYx2Y+iDcuIZztVt1RjsQLFjvMhd1r3UABb9yHTY/ZvTEAZXhJahCyua otgFBI6z3Z6ub1jPN+zYlCr0CrWLuTw8B1foydFt3sLeEBY7C/xu1J+UqBSEc3oOF5Ev 1svWUfCON+j0MIveKyIJV44A9aONqHvtJl3FSuFcpTFEcUNpJ8XYtYZBLTwe5Acpnx6/ zrVZB+2sU739dfN1jRlfrQMKu9OLe5MGZaW6bobOeP/sCDqQJeGhWXHfSrHmLkzgPdvm 1M0AcOT8lwpiEguQ+WwTWI9uev0b3YLG7TjHIe3a0MrdWtzu9XUqi4GfLqkWBYdzN4fA z8MA== X-Gm-Message-State: APzg51CRNIWRLeoc+1xMDMLJj6ociOQkGU78TvjhqybQYktFzNCjZN0x ReTEnlcJcGCnClaHOilhBD1dAuzZ338= X-Google-Smtp-Source: ANB0VdbPzo/fa1nYV529WKuLnBnk/wnBXsX688M3SoP/HDNbQDnI1JvKh6OLonn/rU8y1M8yP0nJEw== X-Received: by 2002:adf:b112:: with SMTP id l18-v6mr6628524wra.101.1535304679970; Sun, 26 Aug 2018 10:31:19 -0700 (PDT) Received: from gumby.homeunix.com ([90.205.16.64]) by smtp.gmail.com with ESMTPSA id n17-v6sm6031026wmc.13.2018.08.26.10.31.18 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 26 Aug 2018 10:31:19 -0700 (PDT) Date: Sun, 26 Aug 2018 18:31:17 +0100 From: RW To: freebsd-questions@freebsd.org Subject: Re: named and ntpd start order in rc.d Message-ID: <20180826183117.5bba87af@gumby.homeunix.com> In-Reply-To: References: X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Aug 2018 17:31:22 -0000 On Sun, 26 Aug 2018 18:34:43 +0200 Andrea Venturoli wrote: > Hello. > > I'm in the same situation described in this bug: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=129146 > > ntpd starts when named is not yet running, fails to resolve its peers > and never works again until I restart it manually. > > That bug (of the 7.0 era) was closed as fixed, since /etc/rc.d/ntpd > requires ntpdate, which in turn required named. > However, the latest statement is not true anymore, today (probably > due to the fact that named is no longer in base). What's in base looks OK rcorder /etc/rc.d/* |egrep 'ntp|unbou|NET' /etc/rc.d/local_unbound /etc/rc.d/NETWORKING /etc/rc.d/ntpdate /etc/rc.d/ntpd local_unbound starts before NETWORKING and ntpdate requires NETWORKING check where bind fits in when you run rcorder /etc/rc.d/* /usr/local/etc/rc.d/* If it's out of correct order I'd suggest opening a new bug report against the bind port. If it's already correct try enabling netwait in rc.conf.