Ursprungligt meddelande
Den 2025-06-28 13:01, Robert Elz skrev:
> Date:Sat, 28 Jun 2025 09:21:16 +
> From:pin
> Message-ID:
>
>
>| why should I avoid it forking to background?
>| Do you think the forking is causing the 'wait' to s
Ursprungligt meddelande
Den 2025-06-28 09:54, RVP skrev:
> On Sat, 28 Jun 2025, pin wrote:
>
> > Yes, I already have that,
> https://codeberg.org/pin/netbsd/src/commit/83b20c65d1b426206d46e3f45c68d8cc345d5d35/etc/rc.conf#L16
> >
>
> Remove the `-b' flag?
Can try when I
On Sat, 28 Jun 2025, pin wrote:
Yes, I already have that,
https://codeberg.org/pin/netbsd/src/commit/83b20c65d1b426206d46e3f45c68d8cc345d5d35/etc/rc.conf#L16
Remove the `-b' flag?
-RVP
t; > Exiting, name server cannot be used: Temporary failure in name resolution
> (2)16 Jun 21:23:49 ntpdate[1082]: name server cannot be used: Temporary
> failure in name resolution (2)
> > /etc/rc.d/ntpdate exited with code 1
> > [...]
> >
> > ntp is running by
used: Temporary failure in
name resolution (2)
/etc/rc.d/ntpdate exited with code 1
[...]
ntp is running by the time I get to X
Any clues?
Desktop users should just add `-w' to make dhcpcd(8) wait for an IP address
to be assigned. That usually fixes this:
```
$ fgrep dhcpcd /etc/rc.conf
> That isn't catch 22, just a deadlock.
You're correct, of course. I should have said "chicken & egg".
> Catch 22 is a very specific kind of problem, where if you want
> something, you can't get it, but if you don't want it, you could.
> Read the book.
Just finished a re-read of "Closing Time"
On Thu, Jun 26, 2025 at 10:25:14PM +, pin wrote:
> Only brought it up since this only started a month or so ago and I
> didn't change my set-up, other than updating along HEAD.
It is kind of a race condition usually, and minor (unrelated) changes
either in the network environment or in the sys
t; failure in name resolution (2)
> > /etc/rc.d/ntpdate exited with code 1
> > [...]
> >
> > ntp is running by the time I get to X
>
> > Any clues?
>
> So all's well, eventually, and you could ignore the initial problem
> (the Temporary failure).
T
gt; > [...]
> > Setting date via ntp.
> > Exiting, name server cannot be used: Temporary failure in name resolution
> (2)16 Jun 21:23:49 ntpdate[1082]: name server cannot be used: Temporary
> failure in name resolution (2)
> > /etc/rc.d/ntpdate exited with
Date:Thu, 26 Jun 2025 18:43:32 +0200 (CEST)
From:Martin Neitzel
Message-ID: <20250626164332.6fbdd24...@hackett.marshlabs.gaertner.de>
Everything you say I agree with, except this:
| ==> catch 22. Neither ntpd nor resolving will start.
That isn't catch 22, just a
> Setting date via ntp.
> Exiting, name server cannot be used: Temporary failure in name resolution
> (2)16 Jun 21:23:49 ntpdate[1082]: name server cannot be used: Temporary
> failure in name resolution (2)
> /etc/rc.d/ntpdate exited with code 1
> [...]
>
> ntp is runnin
> (2)16 Jun 21:23:49 ntpdate[1082]: name server cannot be used: Temporary
> failure in name resolution (2)
> /etc/rc.d/ntpdate exited with code 1
> [...]
>
> ntp is running by the time I get to X
ntpdate runs too early while your DNS server is not yet reachable or (if
you use DHCP
ution (2)
/etc/rc.d/ntpdate exited with code 1
[...]
ntp is running by the time I get to X
Any clues?
Thanks
Skickat från Proton Mail Android
13 matches
Mail list logo
