Date: Fri, 21 Feb 2025 12:40:13 -0800 From: Gleb Smirnoff <glebius@freebsd.org> To: Steve Rikli <sr@genyosha.net> Cc: Rick Macklem <rick.macklem@gmail.com>, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: RFC: mount_nfs failure due to dns not running yet Message-ID: <Z7jkrdce1uEC85Au@cell.glebi.us> In-Reply-To: <Z7fIlo1Dt6AfO%2BZx@dragon.home.genyosha.net> References: <CAM5tNy5wA9DyBP%2BJdq1O6J=VVtXm6Rmm5rtXjJqyJRKvJ8WY=A@mail.gmail.com> <Z7fIlo1Dt6AfO%2BZx@dragon.home.genyosha.net>
index | next in thread | previous in thread | raw e-mail
On Thu, Feb 20, 2025 at 04:28:06PM -0800, Steve Rikli wrote: S> In that area, I'll note FreeBSD rc.d has a "NETWORKING" dependency for S> PROVIDE and REQUIRE, and it's included in scripts like nfsclient, S> mountcritremote et al. However there seems to be no similar dependency S> for something like "NAMESERVICE" (generic, as opposed to "named" S> specifically), and I'm not sure how that might be implemented, even S> assuming it could be useful in a situation like this. Let's once and for all in this email thread rule out, that this is not an rc(8) issue. A host can boot faster than its switch or other networking equipment. No rc(8) magic can help agains that. I mentioned 'late' option as a non-bulletproof workaround for the problem, and that's all. btw, your suggestion for NAMESERVICE provide in rc(8) is a nice one, could be useful for something else, but not for this problem. -- Gleb Smirnoffhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Z7jkrdce1uEC85Au>