On Fri, Feb 21, 2025 at 05:06:16AM -0800, Rick Macklem wrote:
R> Agreed. Unfortunatey, the return values for getaddrinfo(3) do not clearly
R> differentiate between them. I think Gleb's case returns EAI_FAIL, which is
also
R> returned for other failures. I think EAI_NONAME is returned for the case
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
On Fri, Feb 21, 2025 at 12:13 AM Toomas Soome wrote:
>
>
>
> On 21. Feb 2025, at 04:39, Rick Macklem wrote:
>
> On Thu, Feb 20, 2025 at 4:28 PM Steve Rikli wrote:
>
>
> On Wed, Feb 19, 2025 at 02:40:15PM -0800, Rick Macklem wrote:
>
>
> The subject line basically describes the problem glebius@
>
> On 21. Feb 2025, at 04:39, Rick Macklem wrote:
>
> On Thu, Feb 20, 2025 at 4:28 PM Steve Rikli wrote:
>>
>> On Wed, Feb 19, 2025 at 02:40:15PM -0800, Rick Macklem wrote:
>>>
>>> The subject line basically describes the problem glebius@
>>> ran into. When doing an NFS mount in /etc/fstab,
On Thu, Feb 20, 2025 at 4:28 PM Steve Rikli wrote:
>
> On Wed, Feb 19, 2025 at 02:40:15PM -0800, Rick Macklem wrote:
> >
> > The subject line basically describes the problem glebius@
> > ran into. When doing an NFS mount in /etc/fstab, it failed
> > since the DNS service was not yet working and,
On Wed, Feb 19, 2025 at 02:40:15PM -0800, Rick Macklem wrote:
>
> The subject line basically describes the problem glebius@
> ran into. When doing an NFS mount in /etc/fstab, it failed
> since the DNS service was not yet working and, as such,
> the DNS lookup of the server fqdn failed, causing th
Hi,
DNS resolvers can fail transiently, as can UDP. At least some retries seem to
make sense.
(I don’t use NFS; this is a general comment.)
Regards,
Jan M.
> On 19. Feb 2025, at 23:40, Rick Macklem wrote:
>
> Hi,
>
> The subject line basically describes the problem glebius@
> ran into. Wh
Van: Rick Macklem
Datum: woensdag, 19 februari 2025 23:40
Aan: FreeBSD CURRENT
CC: Gleb Smirnoff
Onderwerp: RFC: mount_nfs failure due to dns not running yet
Hi,
The subject line basically describes the problem glebius@
ran into. When doing an NFS mount in /etc/fstab, it failed
since the
On 2/19/25 5:40 PM, Rick Macklem wrote:
Hi,
The subject line basically describes the problem glebius@
ran into. When doing an NFS mount in /etc/fstab, it failed
since the DNS service was not yet working and, as such,
the DNS lookup of the server fqdn failed, causing the mount
to fail. Note that
This situation has existed these past 40 years. You have to put your
ipadress : hostname pairs into /etc/hosts if you dont have accsss to a
working DNS.This is not a bug. Its the way name resolution works.
Den ons 19 feb. 2025 23:40Rick Macklem skrev:
> Hi,
>
> The subject line basically
Hi,
The subject line basically describes the problem glebius@
ran into. When doing an NFS mount in /etc/fstab, it failed
since the DNS service was not yet working and, as such,
the DNS lookup of the server fqdn failed, causing the mount
to fail. Note that this behaviour has existed for decades.
11 matches
Mail list logo