fmtmsg.h(0P)

🦋 fmtmsg.h(0P) — message display structures 💌

okay bestie, so this one lives in the POSIX Programmer's Manual (yes, that manual, the 0P girlies know) ✨

🌸 PROLOG 🌸

This manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (consult the corresponding Linux manual page for details of Linux behavior), or the interface may not be implemented on Linux.

not me warning you upfront that Linux might be doing its own little thing here 💀 the vibes are portable, the behavior is implementation-defined, periodt.

---

👑 NAME 👑

fmtmsg.h — message display structures

---

✨ SYNOPSIS ✨

#include <fmtmsg.h>

---

💖 DESCRIPTION 💖

The <fmtmsg.h> header shall define the following symbolic constants:

• MM_HARD — source of the condition is hardware 🔧
• MM_SOFT — source of the condition is software 💻
• MM_FIRM — source of the condition is firmware 🧚
• MM_APPL — condition detected by application
• MM_UTIL — condition detected by utility
• MM_OPSYS — condition detected by operating system
• MM_RECOVER — recoverable error (we can fix this, bestie 🫶)
• MM_NRECOV — non-recoverable error (it's giving final boss 😭)
• MM_HALT — error causing application to halt
• MM_ERROR — application has encountered a non-fatal fault
• MM_WARNING — application has detected unusual non-error condition
• MM_INFO — informative message
• MM_NOSEV — no severity level provided for the message
• MM_PRINT — display message on standard error
• MM_CONSOLE — display message on system console

The table below indicates the null values and identifiers for fmtmsg() arguments. The <fmtmsg.h> header shall define the symbolic constants in the Identifier column, which shall have the type indicated in the Type column:

• label — Type: char *, Null-Value: (char*)0, Identifier: MM_NULLLBL
• severity — Type: int, Null-Value: 0, Identifier: MM_NULLSEV
• class — Type: long, Null-Value: 0L, Identifier: MM_NULLMC
• text — Type: char *, Null-Value: (char*)0, Identifier: MM_NULLTXT
• action — Type: char *, Null-Value: (char*)0, Identifier: MM_NULLACT
• tag — Type: char *, Null-Value: (char*)0, Identifier: MM_NULLTAG

The <fmtmsg.h> header shall also define the following symbolic constants for use as return values for fmtmsg():

• MM_OK — the function succeeded 🎉
• MM_NOTOK — the function failed completely 💀
• MM_NOMSG — the function was unable to generate a message on standard error, but otherwise succeeded
• MM_NOCON — the function was unable to generate a console message, but otherwise succeeded

The following shall be declared as a function and may also be defined as a macro. A function prototype shall be provided.

int fmtmsg(long, const char *, int,
    const char *, const char *, const char *);

The following sections are informative. (iykyk 🎀)

---

🫶 APPLICATION USAGE 🫶

None.

---

🧠 RATIONALE 🧠

None.

---

🔮 FUTURE DIRECTIONS 🔮

None.

---

🦋 SEE ALSO 🦋

The System Interfaces volume of POSIX.1‐2017, fmtmsg()

---

📜 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 .

---

okay that's the whole page, bestie, and the ✨ cute lil sign-off ✨ at the bottom says this iconic piece of lore is brought to you by IEEE/The Open Group, 2017 — yeah, 2017, she's vintage, she's timeless, she's fmtmsg.h(0P) and she ATE 💅👑🌈