From owner-freebsd-hackers@freebsd.org Thu Sep 12 18:31:12 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0121BD64D4 for ; Thu, 12 Sep 2019 18:31:12 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46TnQl6Bx0z4ZWr; Thu, 12 Sep 2019 18:31:11 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mail-qk1-x730.google.com with SMTP id x134so25498544qkb.0; Thu, 12 Sep 2019 11:31:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PqC51Grddpqtns/+SI5Cor4SAF2Gy183NwNhNsQHQak=; b=gCP4Mz7UqnI08I6aMu9YBZGYwTHlcnlgdhBWJ/Rfs95xSjlSk4V6Kt2ZQTm3V+CbJQ 0jFDYBRbxUQxZ4B6T2pKKCiwJNOCvKcx7u0CRs1bHgYd1Kg9HHa9jnWUwbhKjBc0iWay O89KUBcfOKQZbdIy0CRYoAmxxjUUT2xV6Ll61E2g0r1F1259F4vQsVDWNxEgZOPnMz/j rKFUHfI0dCfwRcyhrXaruE1DlygShHFG8gAuzCJnKsKHNAAUIYY0qXVCCIC2dmKWL4di sV8ICtryR37XCz1N/Z7tMqIwveQC1M2u9Z5aZpEnEj/iHR2M1VwrUyD02IP7tVVcJStt +VCA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PqC51Grddpqtns/+SI5Cor4SAF2Gy183NwNhNsQHQak=; b=csVPMBZ5hBw2GE2NsI7qUqeM3pMQMHvgkAYmTBIMZnXBs7WfgAJ2rZkUfadABkwUOX pv9fmRIIgfkE2L/nvqFef+sCCXLOc9Iv+LhHfdG4QAPdyDKqzWixt1GNdjYj7CxqmJnM Qn0f87Dwvlv0uaAinxU2r4V/1grLIFrdqdXFU/jEU2pR4P3FAr9DEqT2GHWcbTJKIDm5 9xrIn+TGjeJnOCzxbiJxbnodbvJ81VZc7leicCE+UTYWzN5FVUCYIh5wRsPSaJX+CHXO 5qsiiziUoctTSKfdIXYcx8+PUTiKiWqDwH1DvpKgyJX4VcIVJUGyv1l+yMNp3VHIVOMx gXMQ== X-Gm-Message-State: APjAAAVb4j391wco+fVYdNXvyAtFUXf0h7nw5IUdD+EKxbFp2jdCTTeM +FJfduWNEJ0lGi6Dc4PJwIUySxfY5WGBUTUfcQqiCg== X-Google-Smtp-Source: APXvYqymyKejXaafJbIDWUR5BEKyRTWefvqanmX4RebT4Aj/iZlkNU8uJDvfUPIUsWRwsNvc60ZZAImzOF14uhwAE+A= X-Received: by 2002:a37:af87:: with SMTP id y129mr23886628qke.98.1568313070311; Thu, 12 Sep 2019 11:31:10 -0700 (PDT) MIME-Version: 1.0 References: <20190912161342.GB8397@raichu> In-Reply-To: <20190912161342.GB8397@raichu> From: Ryan Stone Date: Thu, 12 Sep 2019 14:30:58 -0400 Message-ID: Subject: Re: /etc/rc.d/dumpon runs before netdump can be configured To: Mark Johnston Cc: freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 46TnQl6Bx0z4ZWr X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-6.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Sep 2019 18:31:12 -0000 The POLA violation would be that kernel panics during some parts of the boot process, like during network configuration, wouldn't be captured. On Thu, Sep 12, 2019 at 12:13 PM Mark Johnston wrote: > > On Thu, Sep 12, 2019 at 11:32:23AM -0400, Ryan Stone wrote: > > Hi everyone, > > > > I recently tried enabling the netdump client on a system via rc.conf. > > However, this isn't working for me because dumpon runs before netif, > > and netdump requires the interface to have been ifconfig'ed up before > > it will allow netdump to be enabled on an interface. > > > > As a result, I get this message during boot, and have to manually run > > "service dumpon start" after boot to get netdump configured. > > > > dumpon: Unable to configure netdump because the interface's link is down. > > > > I'm not sure what the best way to clean this up is. Moving dumpon to > > later in the boot process would be a POLA violation for people dumping > > to disk. Perhaps we need a separate netdump_client rc.d script? > > What exactly is the POLA violation there? > > A separate rc script could be helpful for static network > configurations. For DHCP, I don't see a good solution other than to use > /etc/dhclient-exit-hooks; there is an example for this in the dumpon(8) > man page.