From owner-freebsd-current Tue Oct 17 15:36:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id E6B9B37B4CF for ; Tue, 17 Oct 2000 15:36:53 -0700 (PDT) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id SAA99000 for ; Tue, 17 Oct 2000 18:37:29 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Tue, 17 Oct 2000 18:37:29 -0400 (EDT) From: Adam To: current@freebsd.org Subject: resolver bug since 4.? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I made a typo in a service name today and came across an odd error message that seems to have begun past 3.5-stable sometime. It manifests itself when you try to use a nonexistant service name instead of a port number. I'll file a pr if interest in this issue is lost before a fix is comitted. All 4.x boxen I've tried this on so far: > telnet localhost sdfhsabsdibf localhost: servname not supported for ai_socktype > ftp localhost hsfbidfbwaief ftp: localhost: servname not supported for ai_socktype Bug or not, this message is not very informative. In 3.4-stable ~jan 2000 and 3.5-stable ~Jul 2000, I get: > telnet 0 osals osals: bad port number What would be really nice to see: cheeseball:~ % telnet 0 kjnsbkdfjnbfd tcp/kjnsbkdfjnbfd: unknown service cheeseball:~ % uname -sr NetBSD 1.5F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message