UNLINK(1POSIX)

okay so this is UNLINK(1POSIX), straight out of the POSIX Programmer's Manual. pull up a chair. 🫢


✨ PROLOG ✨

This manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (so consult the corresponding Linux manual page for the details of Linux behavior), or β€” plot twist β€” the interface may not be implemented on Linux. 😭 no cap.


πŸ‘‘ NAME πŸ‘‘

unlink β€” call the unlink() function.

that's the whole job. she calls the function. she leaves. main character energy fr fr. πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

unlink file

πŸ¦‹ DESCRIPTION πŸ¦‹

The unlink utility shall perform the function call, literally:

unlink(file);

also, real talk: a user may need appropriate privileges to invoke the unlink utility. so if it's giving permission-denied, that's not a you problem, that's a privileges problem. πŸ”


🌸 OPTIONS 🌸

None. the options are simply not optioning today. 🫢


πŸ’– OPERANDS πŸ’–

The following operands shall be supported:

  • file β€” the pathname of an existing file.

πŸ’œ STDIN πŸ’œ

Not used.


🧚 INPUT FILES 🧚

Not used.


🌈 ENVIRONMENT VARIABLES 🌈

The following environment variables shall affect the execution of unlink:

  • 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's the main character of the locale world, periodt. πŸ‘‘
  • 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 ⭐

None.


😭 STDERR 😭

The standard error shall be used only for diagnostic messages.


πŸ“ OUTPUT FILES πŸ“

None.


πŸ”₯ EXTENDED DESCRIPTION πŸ”₯

None.


πŸ‘‘ EXIT STATUS πŸ‘‘

The following exit values shall be returned:

  • 0 β€” successful completion. she ate and left no crumbs. πŸ’…
  • >0 β€” an error occurred.

πŸ’€ CONSEQUENCES OF ERRORS πŸ’€

Default.

The following sections are informative. (translation: this is the lore, not the law 🧚✨)


🌸 APPLICATION USAGE 🌸

None.


πŸ’– EXAMPLES πŸ’–

None.


πŸ’œ RATIONALE πŸ’œ

None.


πŸ¦‹ FUTURE DIRECTIONS πŸ¦‹

None.


✨ SEE ALSO ✨

link, rm

The Base Definitions volume of POSIX.1‐2017, Chapter 8, Environment Variables

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


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 .


and that's the page!! source + date, for the record: IEEE/The Open Group, 2017. go forth and unlink responsibly, bestie πŸ«ΆπŸ’–βœ¨
πŸ“¦ where this page comes from