ucspi-proxy(1)

💖 ucspi-proxy — from the General Commands Manual, section 1 🎀

okay bestie, sit down, we're learning ucspi-proxy today and it's actually so simple it's kinda iconic 💅

✨ NAME ✨

ucspi-proxy — copy data between a UCSPI client and server 🦋

🌸 SYNOPSIS 🌸

ucspi-proxy [ -v ] [ -t TIMEOUT ] [ HOST PORT ]

💜 DESCRIPTION 💜

So here's the whole vibe: ucspi-proxy is literally just a simple loop 🔁. It copies data from a UCSPI server (that's file descriptor 0, bestie) over to the client, and it copies data from the client back to the server (that's FD 1). If either socket closes, ucspi-proxy dips out and exits. That's the whole thing. No cap.

And the way that the other ucspi-proxy-* programs are literally based on this exact same simple loop?? They have similar usage. Family resemblance, slay. 👑

Now, if HOST and PORT are given on the command line, ucspi-proxy will make a TCP connection using those parameters. If neither of them is present, it uses file descriptor 6 for the client socket instead — that's the one UCSPI client programs hand you. 🫶

🎀 OPTIONS 🎀

• -l MAXLINE — the maximum length of lines (from either the server or the client) that get copied to the log. Defaults to 64. 📝
• -t TIMEOUT — when it's making a connection, ucspi-proxy waits a maximum of TIMEOUT seconds before it gives up. Defaults to 30. ⏳
• -v — print messages about errors and byte counts. Without this option, ucspi-proxy is completely silent 🤫 (mysterious main character energy, honestly).

🔥 RETURN VALUE 🔥

It exits 0 if a normal end of file was reached on one of the sockets. Otherwise? It exits 1. Simple as that. ✨

🌈 SEE ALSO 🌈

• ucspi-unix
• ucspi-tcp

💀 friendly reminder bestie: no -l in the synopsis line but it's definitely in the options, so don't come for me, I just report what the manpage says fr fr

mwah 💋 that's the whole page — brought to you by the General Commands Manual, ucspi-proxy(1), and yes it's section 1 because it's a command, periodt 🎀✨💖