UPSCLI_STR_CONTAINS_(3)

💅 UPSCLI_STR_CONTAINS_(3) 💅

okay bestie, so this one lives in the NUT Manual (yes, that's Network UPS Tools, and yes, the acronym is iconic and we're not changing it). Let's get into it ✨

---

🌸 NAME 🌸

upscli_str_contains_token — the lil function that checks whether an unique token is actually chilling inside your string 🕵️‍♀️

---

🎀 SYNOPSIS 🎀

#include <upsclient.h>

int     upscli_str_contains_token(const char *string, const char *token);

---

🦋 DESCRIPTION 🦋

okay so picture this. upscli_str_contains_token() takes two pointers, right?

Pointer number one is tgt, and it points at a caller-provided const char * buffer. That buffer is made up of unique tokens, and those tokens are separated by single space characters (that's ASCII 0x20, bestie, the regular space, no fancy whitespace shenanigans 💀).

Pointer number two is token, and it points at a presumed-contiguous token value — like, the token you're hoping to find in that tgt buffer.

and then the function is literally just: is it in there or not? vibe check complete ✅

---

🔥 RETURN VALUE 🔥

upscli_str_contains_token() hands you back a numeric code, and here's how to read it:

• non-zero if the token value was found in the tgt buffer (it might be surrounded by space characters, or it might be sitting right at the start or the end of the string — all of those count, slay ✨)
• 0 if the token was not found, or if either token or tgt string was NULL or empty 🫠

bestie please check your empty strings and NULLs, the function is not gonna be nice about it, it's just gonna return 0 and move on 💀

---

👑 SEE ALSO 👑

• upscli_str_add_unique_token(3) — the other token girlie, go say hi 🫶

---

and that's the whole page, no cap 💖 this was Network UPS Tools 2.8.5, dated 06/21/2026 — iconic version, iconic date, periodt 🌈⭐