Sure, now that I am online, I have a working resolver.
But not when I made the report. I was offline.
Anyway it is 100% the fault of the program for
not having been tested offline without a resolver running.
On Sun, 24 May 2020 at 01:38:14 +0200, Guilhem Moulin wrote:
> That error should probably not be fatal
FTR that's in report_sock().
--
Guilhem.
signature.asc
Description: PGP signature
Control: retitle -1 -v yields fatal name resolution errors
Control: tag -1 upstream
On Sat, 23 May 2020 at 18:33:38 +0800, Dan Jacobson wrote:
> $ nc -v -l -p 60111
> nc: getnameinfo: Temporary failure in name resolution
Do you have a working resolver on that host? I can't reproduce this
with a
Package: netcat-openbsd
Version: 1.206-1
File: /bin/nc.openbsd
$ man nc
-v Produce more verbose output.
but
$ nc -v -l -p 60111
nc: getnameinfo: Temporary failure in name resolution
and it dies. That's crazy.
$ nc.traditional -v -l -p 60111
listening on [any] 60111 ...
That's better.
4 matches
Mail list logo
