IPCRM(1P)

💖 IPCRM(1P) — the POSIX Programmer's Manual, but make it make sense 💖

okay bestie, before we even start: this page lives in the POSIX Programmer's Manual. That means the Linux version of this interface might act differently (so go peek at the matching Linux man page for the tea on Linux behavior), or honestly it might just not be implemented on Linux at all. 🙈 No cap.

---

✨ NAME ✨

ipcrm — remove an XSI message queue, semaphore set, or shared memory segment identifier

---

🎀 SYNOPSIS 🎀

ipcrm [-q msgid|-Q msgkey|-s semid|-S semkey|-m shmid|-M shmkey]...

---

🦋 DESCRIPTION 🦋

So ipcrm shall remove zero or more message queues, semaphore sets, or shared memory segments. Which interprocess communication facilities get removed? That's entirely decided by the options you pass. You pick, bestie. 💅

And here's the gatekeeping part: only a user with appropriate privileges shall be allowed to remove an interprocess communication facility that wasn't created by — or owned by — the user invoking ipcrm. Not yours? Not your business, unless you've got the privileges. Periodt.

---

🌸 OPTIONS 🌸

The ipcrm utility shall conform to the Base Definitions volume of POSIX.1‐2017, Section 12.2, Utility Syntax Guidelines.

The following options shall be supported:

• -q msgid — Remove the message queue identifier msgid from the system, and destroy the message queue and the data structure associated with it. Gone. Bye. 💀
• -m shmid — Remove the shared memory identifier shmid from the system. The shared memory segment and its data structure shall be destroyed after the last detach. (key word: after, okay? it's patient.)
• -s semid — Remove the semaphore identifier semid from the system, and destroy the set of semaphores and the data structure associated with it.
• -Q msgkey — Remove the message queue identifier that was created with key msgkey from the system, and destroy the message queue and the data structure associated with it.
• -M shmkey — Remove the shared memory identifier that was created with key shmkey from the system. The shared memory segment and its data structure shall be destroyed after the last detach.
• -S semkey — Remove the semaphore identifier that was created with key semkey from the system, and destroy the set of semaphores and the data structure associated with it.

lowkey notice the lowercase/uppercase thing: lowercase = you're giving an id, uppercase = you're giving a key. That's the whole vibe. iykyk.

---

🧚 OPERANDS 🧚

None. Zero. Nothing. There's no operands section drama here. ✨

---

⭐ STDIN ⭐

Not used. She's not listening. 🙈

---

🍓 INPUT FILES 🍓

None.

---

🌈 ENVIRONMENT VARIABLES 🌈

The following environment variables shall affect the execution of ipcrm:

• LANG — Provide a default value for the internationalization variables that are unset or null. (See the Base Definitions volume of POSIX.1‐2017, Section 8.2, Internationalization Variables for the precedence of internationalization variables used to determine the values of locale categories.)
• LC_ALL — If set to a non-empty string value, override the values of all the other internationalization variables. She said what she said. 👑
• LC_CTYPE — Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi-byte characters in arguments).
• LC_MESSAGES — Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error.
• NLSPATH — Determine the location of message catalogs for the processing of LC_MESSAGES.

---

💜 ASYNCHRONOUS EVENTS 💜

Default.

---

🫶 STDOUT 🫶

Not used. She's silent, she's mysterious, she's just doing the job. 💅

---

😭 STDERR 😭

The standard error shall be used only for diagnostic messages. So if something shows up there, bestie... something happened.

---

🎀 OUTPUT FILES 🎀

None.

---

🌸 EXTENDED DESCRIPTION 🌸

None.

---

🔥 EXIT STATUS 🔥

The following exit values shall be returned:

1. 0 — Successful completion. slay. ✨
2. >0 — An error occurred.

---

💀 CONSEQUENCES OF ERRORS 💀

Default.

The following sections are informative. (That means they're the commentary track, not the actual rules. 🎧)

---

👑 APPLICATION USAGE 👑

None.

---

🦋 EXAMPLES 🦋

None. (I know. I wanted examples too. 😭)

---

💜 RATIONALE 💜

None.

---

🌈 FUTURE DIRECTIONS 🌈

None.

---

⭐ SEE ALSO ⭐

• ipcs
• The Base Definitions volume of POSIX.1‐2017, Chapter 8, Environment Variables, Section 12.2, Utility Syntax Guidelines
• The System Interfaces volume of POSIX.1‐2017, msgctl(), semctl(), shmctl()

---

🎀 COPYRIGHT 🎀

Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1-2017, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html .

Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .

---

ok that's the whole page, no crumbs left 💅

and finally, the receipts: this was IEEE/The Open Group, dated 2017, and the page answers to the name IPCRM(1P). mwah. 🫶✨