Date: Thu, 24 May 2001 13:24:03 -0700 (PDT) From: Matt Dillon <dillon@earth.backplane.com> To: "Jacques A. Vidrine" <n@nectar.com> Cc: Gordon Tetlow <gordont@bluemtn.net>, freebsd-hackers@FreeBSD.ORG Subject: Re: telnet to AF_UNIX sockets [PATCH] Message-ID: <200105242024.f4OKO3530561@earth.backplane.com> References: <20010523220844.A26487@shade.nectar.com> <Pine.BSF.4.33.0105241105210.76720-100000@sdmail0.sd.bmarts.com> <20010524132144.A14177@shade.nectar.com>
next in thread | previous in thread | raw e-mail | index | archive | help
:Because `all telnet really does is connect to sockets' is patently
:false. Check out the nearly 100 RFCs detailing the TELNET protocol.
:Almost none of these make much sense to do over UNIX domain sockets
:[1].
Huh? Oh yah, *that* protocol. Telnet only does that if the server
is a telnetd. Otherwise it's just straight character I/O. Any
experienced sysad knows this from telneting to the web server or
smtp server or pop server, etc etc etc. Being able to telnet to a unix
domain socket is no different.
Unix domain sockets are a good test of experience. They are obscure
enough that many people don't even realize they exist (and even fewer
know that you can pass file descriptors over them). But unix-domain
sockets are extremely useful in all manner of applications and the
more sophisticated programmers use them all over the place. Being able
to telnet to one is natural. Over the years I've probably
written the 'connect to unix domain socket' program 50 times because
it wasn't standard in a system. Now it is. Yahhh.
-Matt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200105242024.f4OKO3530561>