MEMTOUCH(1)

πŸ’… MEMTOUCH β€” the memtouch manual, bestie edition ✨

okay so you found yourself in the libmemcached-awesome section of the manual (section 1, the commands section, iykyk) and the page is literally called memtouch. buckle up, it's short and it's cute and we're gonna get through it together 🫢


✨ NAME ✨

memtouch β€” the libmemcached documentation page for memtouch. that's it, that's the name section, she's brief πŸ’€


🌸 SYNOPSIS 🌸

memtouch [options] <key>

you give her some options, you give her a key, she does her thing. no cap πŸŽ€


πŸ’– DESCRIPTION πŸ’–

memtouch does a "touch" on the key you specify. like, it reaches out and touches it. gently. that's the whole job and honestly? iconic. slay. 🌈


πŸ’… OPTIONS πŸ’…

  • -h, --help β€” shows you the help. bestie behavior 🫢
  • -V, --version β€” shows you the version. so you know exactly which girl you're talking to.
  • -q, --quiet β€” operate quietly 🀫 like, keep it lowkey.
  • -v, --verbose β€” operate more verbosely. she will tell you EVERYTHING and honestly we love a yapper πŸ’¬
  • -d, --debug β€” this is literally the same thing as -v, --verbose. see above, bestie ✨
  • -s, --servers <list of servers> β€” specify the list of servers, formatted like this: hostname[:port][,hostname[:port]...]. yes the port is optional, yes you can comma-separate a whole roster, go off πŸ‘‘
  • -n, --non-blocking β€” enables non-blocking operations. she does not wait around, she has places to be πŸ’…
  • -N, --tcp-nodelay β€” disables Nagle's algorithm. yes bestie we're turning Nagle OFF, no buffering-and-waiting drama today πŸ”₯
  • -b, --binary β€” enables the binary protocol. bytes only, no side quests 🌸
  • -B, --buffer β€” buffers requests. she's collecting them, she'll deal with them later πŸŽ€
  • -u, --username <username> β€” use username for SASL authentication. πŸ’œ
  • -p, --password <password> β€” use password for SASL authentication. πŸ” keep it secret, keep it safe.
  • -H, --hash <algorithm> β€” use algorithm as the key hash algo. check out memcached_behavior_t::MEMCACHED_BEHAVIOR_HASH <#_CPPv4N20memcached_behavior_t23MEMCACHED_BEHAVIOR_HASHE> for the full tea ✨
  • -e, --expire <expiration> β€” use expiration seconds (or, plot twist, a UNIX timestamp). either way she knows when it's over ⏰

🌈 ENVIRONMENT 🌈

  • MEMCACHED_SERVERS β€” specify a list of servers. yes, environment-variable style, she reads the room before you even type anything πŸ¦‹

πŸŽ€ NOTES πŸŽ€

🧚 PROGRAM PREFIX 🧚

the prefix of this program is variable, meaning it can be configured at build time. not fixed. not locked in. she's flexible like that πŸ’

usually the client programs of libmemcached-awesome are prefixed with mem, like memcat or memcp. cute, consistent, we stan 🫢

it can be configured, though, to replace the prefix with something else like mc. and in case of that, the client programs of libmemcached-awesome would be called mccat, mccp, etc. respectively. so if you're staring at an mc-flavored binary like πŸ‘οΈπŸ‘„πŸ‘οΈ β€” now you know, periodt.


πŸ‘‘ SEE ALSO πŸ‘‘

also these two, bestie (the links are literally empty in the source, not my fault, blame the manpage):

  • C/C++ Client Library for memcached
  • Update expiration on a key

πŸ’– reminder for the girlies: this whole page is for memtouch, section 1 of the manual, and every flag above does EXACTLY what it says, no more no less. no invented behavior, no guessing, no cap. πŸ”₯

and that's the page!! this vibe check was brought to you by version 1.1, dated Jul 24, 2026, from libmemcached-awesome. bye bestie, go touch a key πŸ’…βœ¨πŸ¦‹

πŸ“¦ where this page comes from