Date: Sat, 22 Jul 2006 07:46:39 GMT From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: FreeBSD-gnats-submit@FreeBSD.org Subject: bin/100709: getaddrinfo(3) should return TTL info Message-ID: <200607220746.k6M7kd0b068120@critter.freebsd.dk> Resent-Message-ID: <200607220750.k6M7oGGa034656@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 100709 >Category: bin >Synopsis: getaddrinfo(3) should return TTL info >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sat Jul 22 07:50:16 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Poul-Henning Kamp >Release: FreeBSD 7.0-CURRENT i386 >Organization: >Environment: System: FreeBSD critter.freebsd.dk 7.0-CURRENT FreeBSD 7.0-CURRENT #5: Wed Jul 5 22:14:32 UTC 2006 root@critter.freebsd.dk:/critter/obj/critter/src/sys/TP41P i386 >Description: Why doesn't getaddrinfo() return the time-to-live timestamp from DNS lookups ? That would be very convenient information for long-running daemons so they don't have to do lookups more than necessary. For file based or numeric inputs, the ttl could be zero to indicate "unknown". >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200607220746.k6M7kd0b068120>