TCPCONNECT(1)

okay bestie, listen up 👑 the header at the top of this page literally says TCPCONNECT(1) and it lives in the General Commands Manual section, but the NAME line down below is out here calling itself tcplisten — yes, fr fr, that's just what it says, I'm not editing the source, I'm just telling you what's on the page 🫶

✨ NAME ✨

tcplisten — a general TCP/IP server 🦋

🌸 SYNOPSIS 🌸

tcplisten [-irv] [localaddr] port

💅 DESCRIPTION 💅

So basically tcplisten just... waits. Patiently. Iconic behavior honestly. It sits there waiting for a TCP/IP connection on port. ⭐

If you hand it a localaddr parameter, it will bind to that IP address specifically. If you don't, no stress — it'll accept connections to any of the local machine's IP addresses. 🌈

Then here's the tea ☕: data coming in from the client gets printed on standard output, and data read from standard input gets sent to the client. It's giving full duplex main character energy.

When end-of-file is reached on both standard input and the TCP/IP connection, tcplisten terminates. Both. Not one. Both. 😭

🎀 OPTIONS 🎀

• -i — Terminate at end-of-file on standard input; don't wait for the client to close the connection. ✨
• -r — Terminate when the remote client closes the connection; don't wait for end-of-file on standard input. 💫
• -v — Verbose mode. Prints a message to standard error about the origins (host and port) of the client. 👀

🦋 SEE ALSO 🦋

tcpconnect(1), telnet(1), mini-inetd(1), tcpbug(1).

go read those too, they're the friend group 💖

💀 BUGS 💀

The names of the options are not yet finalized, and may change at a future release. so like... don't get attached to -i, -r and -v okay?? they could rebrand at any moment 🙈

and that's the whole page bestie, no cap, you're basically a TCP/IP server whisperer now 💜

this little love letter is from 1997 April 13 — yeah she's a 90s baby and she ate 🎀✨