Date: Tue, 17 Oct 2000 18:37:29 -0400 (EDT) From: Adam <bsdx@looksharp.net> To: current@freebsd.org Subject: resolver bug since 4.? Message-ID: <Pine.BSF.4.21.0010171829050.84848-100000@turtle.looksharp.net>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0010171829050.84848-100000>