TMPNAM(3P)
π tmpnam(3P) β the create-a-name-for-a-temporary-file situation π
okay so bestie, welcome to TMPNAM(3P) from the POSIX Programmer's Manual. Buckle up, because this one is short but it is messy. π«Ά
β¨ PROLOG β¨
real talk first: this manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (so pls consult the corresponding Linux manual page for the tea on Linux behavior), or the interface may not even be implemented on Linux at all. π
πΈ NAME πΈ
tmpnam β create a name for a temporary file
π SYNOPSIS π
#include <stdio.h>
char *tmpnam(char *s);
π¦ DESCRIPTION π¦
Okay so the functionality described on this reference page is aligned with the ISO C standard. Any conflict between the requirements described here and the ISO C standard is unintentional β no drama intended, fr fr. This volume of POSIX.1β2017 defers to the ISO C standard.
The tmpnam() function shall generate a string that is a valid pathname that does not name an existing file. The function is potentially capable of generating {TMP_MAX} different strings, but any or all of them may already be in use by existing files and thus not be suitable return values. π it's giving "technically valid, practically chaotic".
The tmpnam() function generates a different string each time it is called from the same process, up to {TMP_MAX} times. If it is called more than {TMP_MAX} times, the behavior is implementation-defined β iykyk, that means nobody promised you anything.
The implementation shall behave as if no function defined in this volume of POSIX.1β2017, except tempnam(), calls tmpnam().
β οΈ Also,tmpnam()need not be thread-safe if called with aNULLparameter. Not me warning you twice. π
π RETURN VALUE π
Upon successful completion, tmpnam() shall return a pointer to a string. If no suitable string can be generated, the tmpnam() function shall return a null pointer.
If the argument s is a null pointer, tmpnam() shall leave its result in an internal static object and return a pointer to that object. Subsequent calls to tmpnam() may modify the same object β so that pointer you're holding? Yeah, it's not yours forever bestie. π
If the argument s is not a null pointer, it is presumed to point to an array of at least L_tmpnam chars; tmpnam() shall write its result in that array and shall return the argument as its value. Slay, it just hands you back what you gave it. β¨
π ERRORS π
No errors are defined. π Periodt.
The following sections are informative.
π EXAMPLES π
Generating a Pathname π§
The following example generates a unique pathname and stores it in the array pointed to by ptr.
#include <stdio.h>
...
char pathname[L_tmpnam+1];
char *ptr;
ptr = tmpnam(pathname);
π APPLICATION USAGE π
Okay bestie, listen. This function only creates pathnames. It is the application's responsibility to create and remove the files. Not the function's problem. π«Ά
π Between the time a pathname is created and the file is opened, it is possible for some other process to create a file with the same name. Classic race condition main character energy.
Applications may find tmpfile() more useful.
Applications should use the tmpfile(), mkstemp(), or mkdtemp() functions instead of the obsolescent tmpnam() function. Yeah. It's giving deprecated. It's giving "we're not mad, we're just disappointed". π
π RATIONALE π
None. Nothing. Nada. The committee said no thoughts, head empty. β¨
π₯ FUTURE DIRECTIONS π₯
The tmpnam() function may be removed in a future version. So likeβ¦ don't get attached. π
β SEE ALSO β
fopen()open()mkdtemp()tempnam()tmpfile()unlink()
The Base Definitions volume of POSIX.1β2017, <stdio.h>
πΈ 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 .
and that's the whole page, bestie!! shoutout to IEEE/The Open Group, 2017 for the source and date β this was TMPNAM(3P) and you ate that. πβ¨ππ¦πΈπ
π«Ά
π¦ where this page comes from
- alpine 3.22: man-pages-posix 2017a-r0 Β· custom
- alpine 3.23: man-pages-posix 2017a-r0 Β· custom
- alpine 3.24: man-pages-posix 2017a-r0 Β· custom
- arch rolling: man-pages 6.19-1
- arch rolling: man-pages 6.20-1 Β· BSD-2-Clause AND BSD-3-Clause AND BSD-4.3TAHOE AND BSD-4-Clause-UC AND GPL-1.0-or-later AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-or-later AND LGPL-3.0-linking-exception AND LGPL-3.0-or-later AND LicenseRef-Public-Domain AND LicenseRef-UltraPermissive AND Linux-man-pages-1-para AND Linux-man-pages-copyleft AND Linux-man-pages-copyleft-2-para AND Linux-man-pages-copyleft-var AND MIT AND Spencer-94
- nixpkgs unstable: man-pages-posix 2017a
- opensuse-leap 16.0: man-pages-posix 2017a-160000.4.1 Β· SUSE-IEEE
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms