/etc/rc.d/dumpon runs before netdump can be configured

[Mark Johnston]

On Thu, Sep 12, 2019 at 02:30:58PM -0400, Ryan Stone wrote:
> The POLA violation would be that kernel panics during some parts of
> the boot process, like during network configuration, wouldn't be
> captured.

I think it would reasonable to add a dumponlate, following the pattern
of mountlate and swaplate, to handle this.

> On Thu, Sep 12, 2019 at 12:13 PM Mark Johnston <markj at freebsd.org> 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.