explain_tmpfile(3)					     Library Functions Manual						explain_tmpfile(3)

NAME

       explain_tmpfile - explain tmpfile(3) errors

SYNOPSIS

       #include <libexplain/tmpfile.h>
       const char *explain_tmpfile(void);
       const char *explain_errno_tmpfile(int errnum, void);
       void explain_message_tmpfile(char *message, int message_size, void);
       void explain_message_errno_tmpfile(char *message, int message_size, int errnum, void);

DESCRIPTION

       These functions may be used to obtain explanations for errors returned by the tmpfile(3) system call.

   explain_tmpfile
       const char *explain_tmpfile(void);

       The  explain_tmpfile  function  is  used to obtain an explanation of an error returned by the tmpfile(3) system call. The least the message
       will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail.

       The errno global variable will be used to obtain the error value to be decoded.

       Returns:
	       The message explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer  in  their
	       argument  list.	 This  will  be  overwritten by the next call to any libexplain function which shares this buffer, including other
	       threads.

       Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library.

       Example: This function is intended to be used in a fashion similar to the following example:
	      FILE *result = tmpfile();
	      if (!result)
	      {
		  fprintf(stderr, "%s
", explain_tmpfile());
		  exit(EXIT_FAILURE);
	      }

       The above code example is available pre-packaged as the explain_tmpfile_or_die(3) function.

   explain_errno_tmpfile
       const char *explain_errno_tmpfile(int errnum, void);

       The explain_errno_tmpfile function is used to obtain an explanation of an error returned by the tmpfile(3) system call. The least the  mes-
       sage will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail.

       errnum  The  error value to be decoded, usually obtained from the errno global variable just before this function is called. This is neces-
	       sary if you need to call any code between the system call to be explained and this function, because many libc functions will alter
	       the value of errno.

       Returns:
	       The  message  explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer in their
	       argument list.  This will be overwritten by the next call to any libexplain function which  shares  this  buffer,  including  other
	       threads.

       Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library.

       Example: This function is intended to be used in a fashion similar to the following example:
	      FILE *result = tmpfile();
	      if (!result)
	      {
		  int err = errno;
		  fprintf(stderr, "%s
", explain_errno_tmpfile(err, ));
		  exit(EXIT_FAILURE);
	      }

       The above code example is available pre-packaged as the explain_tmpfile_or_die(3) function.

   explain_message_tmpfile
       void explain_message_tmpfile(char *message, int message_size, void);

       The  explain_message_tmpfile  function  is  used to obtain an explanation of an error returned by the tmpfile(3) system call. The least the
       message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail.

       The errno global variable will be used to obtain the error value to be decoded.

       message The location in which to store the returned message. If a suitable message return buffer is supplied, this function is thread safe.

       message_size
	       The size in bytes of the location in which to store the returned message.

       Example: This function is intended to be used in a fashion similar to the following example:
	      FILE *result = tmpfile();
	      if (!result)
	      {
		  char message[3000];
		  explain_message_tmpfile(message, sizeof(message), );
		  fprintf(stderr, "%s
", message);
		  exit(EXIT_FAILURE);
	      }

       The above code example is available pre-packaged as the explain_tmpfile_or_die(3) function.

   explain_message_errno_tmpfile
       void explain_message_errno_tmpfile(char *message, int message_size, int errnum, void);

       The explain_message_errno_tmpfile function is used to obtain an explanation of an error returned by the tmpfile(3) system call.	The  least
       the  message  will  contain  is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more
       detail.

       message The location in which to store the returned message. If a suitable message return buffer is supplied, this function is thread safe.

       message_size
	       The size in bytes of the location in which to store the returned message.

       errnum  The error value to be decoded, usually obtained from the errno global variable just before this function is called. This is  neces-
	       sary if you need to call any code between the system call to be explained and this function, because many libc functions will alter
	       the value of errno.

       Example: This function is intended to be used in a fashion similar to the following example:
	      FILE *result = tmpfile();
	      if (!result)
	      {
		  int err = errno;
		  char message[3000];
		  explain_message_errno_tmpfile(message, sizeof(message), err, );
		  fprintf(stderr, "%s
", message);
		  exit(EXIT_FAILURE);
	      }

       The above code example is available pre-packaged as the explain_tmpfile_or_die(3) function.

SEE ALSO

       tmpfile(3)
	       create a temporary file

       explain_tmpfile_or_die(3)
	       create a temporary file and report errors

COPYRIGHT

       libexplain version 0.52
       Copyright (C) 2009 Peter Miller

																explain_tmpfile(3)