diff options
| author | Ruslan Ermilov <ru@FreeBSD.org> | 2005-01-20 09:17:07 +0000 |
|---|---|---|
| committer | Ruslan Ermilov <ru@FreeBSD.org> | 2005-01-20 09:17:07 +0000 |
| commit | 24a0682c6465290759ed0b09ea16e40e7cd47053 (patch) | |
| tree | 13c84f0554aefe96321f671bc8860f5e9f184a5a /lib/libc/stdio/tmpnam.3 | |
| parent | e1239d17fe51ff52f68635ebbb01e77d58371618 (diff) | |
Notes
Diffstat (limited to 'lib/libc/stdio/tmpnam.3')
| -rw-r--r-- | lib/libc/stdio/tmpnam.3 | 48 |
1 files changed, 24 insertions, 24 deletions
diff --git a/lib/libc/stdio/tmpnam.3 b/lib/libc/stdio/tmpnam.3 index 7937a0ab6d0a..825c3c9b07e7 100644 --- a/lib/libc/stdio/tmpnam.3 +++ b/lib/libc/stdio/tmpnam.3 @@ -156,6 +156,30 @@ return a pointer to a file name on success, and a .Dv NULL pointer on error. +.Sh COMPATIBILITY +These interfaces are provided from System V and +.Tn ANSI +compatibility only. +.Pp +Most historic implementations of these functions provide +only a limited number of possible temporary file names +(usually 26) +before file names will start being recycled. +System V implementations of these functions +(and of +.Xr mktemp 3 ) +use the +.Xr access 2 +system call to determine whether or not the temporary file +may be created. +This has obvious ramifications for setuid or setgid programs, +complicating the portable use of these interfaces in such programs. +.Pp +The +.Fn tmpfile +interface should not be used in software expected to be used on other systems +if there is any possibility that the user does not wish the temporary file to +be publicly readable and writable. .Sh ERRORS The .Fn tmpfile @@ -202,30 +226,6 @@ It is strongly suggested that be used in place of these functions. (See the FSA.) -.Sh COMPATIBILITY -These interfaces are provided from System V and -.Tn ANSI -compatibility only. -.Pp -Most historic implementations of these functions provide -only a limited number of possible temporary file names -(usually 26) -before file names will start being recycled. -System V implementations of these functions -(and of -.Xr mktemp 3 ) -use the -.Xr access 2 -system call to determine whether or not the temporary file -may be created. -This has obvious ramifications for setuid or setgid programs, -complicating the portable use of these interfaces in such programs. -.Pp -The -.Fn tmpfile -interface should not be used in software expected to be used on other systems -if there is any possibility that the user does not wish the temporary file to -be publicly readable and writable. .Sh SEE ALSO .Xr mkstemp 3 , .Xr mktemp 3 |
