GETEGID(3POSIX)

📦 version 2017a, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu resolute, ubuntu stonking

🎀 GETEGID(3POSIX) 🎀

okay so real talk before anything else — this page is part of the POSIX Programmer's Manual, and there's a lil disclaimer at the top that you genuinely need to read, no skipping bestie 🙈

⚠️ 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.

that's the PROLOG, that's the vibe, now let's GO 🦋

🌸 NAME 🌸

getegid — get the effective group ID

that's it. that's her whole job. icon behaviour honestly 👑

✨ SYNOPSIS ✨

#include <unistd.h>

gid_t getegid(void);

💖 DESCRIPTION 💖

okay so the getegid() function shall return the effective group ID of the calling process. simple as.

and the second part is the one people forget — getegid() shall not modify errno. like, she does not touch it. not her business. hands off. 🫶

👑 RETURN VALUE 👑

getegid() shall always be successful, and there is no return value reserved to indicate an error. she literally cannot fail. main character energy, zero flop era 💅

💀 ERRORS 💀

No errors are defined.

The following sections are informative.

🍓 EXAMPLES 🍓

None.

😭 literally nothing here. no example. empty. void. we move.

🧚 APPLICATION USAGE 🧚

None.

again — nothing. the page said what it said and dipped 🦋

🔥 RATIONALE 🔥

okay here's the lore, bestie.

In a conforming environment, getegid() will always succeed. full stop.

BUT — it is possible for implementations to provide an extension where a process in a non-conforming environment will not be associated with a user or group ID. like, the process just isn't anybody's. no user, no group. ghost process 🫥

and it is recommended that such implementations return (gid_t)-1 and set errno to indicate such an environment. and here's the cute part — doing so does not violate this standard, since such an environment is already an extension. so they're allowed. it's fine. no cap.

🌈 FUTURE DIRECTIONS 🌈

None.

💜 SEE ALSO 💜

  • geteuid()
  • getgid()
  • getuid()
  • setegid()
  • seteuid()
  • setgid()
  • setregid()
  • setreuid()
  • setuid()

also, from the Base Definitions volume of POSIX.1‐2017: <sys_types.h> and <unistd.h> — go read those headers, they're giving reference material 💖

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 .

aaaand that's the page bestie 🎀 this one came to you courtesy of IEEE/The Open Group, 2017 — IEEE/The Open Group 2017 GETEGID(3POSIX) — and yeah she's short, but she's perfect. periodt. 💅✨

📦 where this page comes from