tipc_sendstream(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’Œ tipc_sendstream(9) β€” bestie edition πŸ’Œ

okay so this is tipc_sendstream, straight out of the Kernel API Manual section of the man pages, and yes we are absolutely going to get into it πŸ’…


✨ NAME ✨

tipc_sendstream β€” the girl whose whole job is sending stream-oriented data πŸ¦‹


✨ SYNOPSIS ✨

int tipc_sendstream (struct socket *sock , struct msghdr *m , size_t dsz
);

that's it. three (3) little parameters. she's lowkey minimal and that's the vibe πŸŽ€


✨ ARGUMENTS ✨

  • sock β€” the socket structure, aka the main character of this whole operation πŸ‘‘
  • m β€” the data we're sending, literally the whole point πŸ“
  • dsz β€” total length of data to be transmitted, so: how many bytes are we actually putting out there, be honest 🌸

✨ DESCRIPTION ✨

so like. this one is used for SOCK_STREAM data. that's the entire description bestie, the man page said it in one line and we respect the confidence 😭 it's giving "I said what I said" and honestly? slay πŸ”₯


✨ RETURN ✨

  • on success (or partial success, because we're realistic) β†’ you get the number of bytes sent πŸ’–
  • if no data got sent β†’ you get an errno instead πŸ™ˆ
not me checking the return value every single time. please check your return values bestie, partial success is still success and you need to know which one you got 🫢

✨ SEE ALSO ✨

the full group chat, in order, no gatekeeping ⭐

like I said. full group chat. every single one made the list and we're not leaving anyone on read πŸ‘‘πŸ’œ


and that's the whole page, no cap πŸ’«

this lil masterpiece lives in ./net/tipc, dated October 2026, and it's tipc_sendstream(9) forever and always β€” mwah πŸ’‹πŸŽ€βœ¨

πŸ“¦ where this page comes from