1explain_uname(3) Library Functions Manual explain_uname(3)
2
6 explain_uname - explain uname(2) errors
7
9 #include <libexplain/uname.h>
10 const char *explain_uname(struct utsname *data);
11 const char *explain_errno_uname(int errnum, struct utsname *data);
12 void explain_message_uname(char *message, int message_size, struct
13 utsname *data);
14 void explain_message_errno_uname(char *message, int message_size, int
15 errnum, struct utsname *data);
16
18 These functions may be used to obtain explanations for errors returned
19 by the uname(2) system call.
20 explain_uname
22 const char *explain_uname(struct utsname *data);
23 The explain_uname function is used to obtain an explanation of an error
25 returned by the uname(2) system call. The least the message will con‐
26 tain is the value of strerror(errno), but usually it will do much bet‐
27 ter, and indicate the underlying cause in more detail.
28 The errno global variable will be used to obtain the error value to be
30 decoded.
31 data The original data, exactly as passed to the uname(2) system
33 call.
34 Returns:
36 The message explaining the error. This message buffer is shared
37 by all libexplain functions which do not supply a buffer in
38 their argument list. This will be overwritten by the next call
39 to any libexplain function which shares this buffer, including
40 other threads.
41 Note: This function is not thread safe, because it shares a return buf‐
43 fer across all threads, and many other functions in this library.
44 Example: This function is intended to be used in a fashion similar to
46 the following example:
47 if (uname(data) < 0)
48 {
49 fprintf(stderr, "%s\n", explain_uname(data));
50 exit(EXIT_FAILURE);
51 }
52 The above code example is available pre-packaged as the
54 explain_uname_or_die(3) function.
55 explain_errno_uname
57 const char *explain_errno_uname(int errnum, struct utsname *data);
58 The explain_errno_uname function is used to obtain an explanation of an
60 error returned by the uname(2) system call. The least the message will
61 contain is the value of strerror(errno), but usually it will do much
62 better, and indicate the underlying cause in more detail.
63 errnum The error value to be decoded, usually obtained from the errno
65 global variable just before this function is called. This is
66 necessary if you need to call any code between the system call
67 to be explained and this function, because many libc functions
68 will alter the value of errno.
69 data The original data, exactly as passed to the uname(2) system
71 call.
72 Returns:
74 The message explaining the error. This message buffer is shared
75 by all libexplain functions which do not supply a buffer in
76 their argument list. This will be overwritten by the next call
77 to any libexplain function which shares this buffer, including
78 other threads.
79 Note: This function is not thread safe, because it shares a return buf‐
81 fer across all threads, and many other functions in this library.
82 Example: This function is intended to be used in a fashion similar to
84 the following example:
85 if (uname(data) < 0)
86 {
87 int err = errno;
88 fprintf(stderr, "%s\n", explain_errno_uname(err, data));
89 exit(EXIT_FAILURE);
90 }
91 The above code example is available pre-packaged as the
93 explain_uname_or_die(3) function.
94 explain_message_uname
96 void explain_message_uname(char *message, int message_size, struct
97 utsname *data);
98 The explain_message_uname function is used to obtain an explanation of
100 an error returned by the uname(2) system call. The least the message
101 will contain is the value of strerror(errno), but usually it will do
102 much better, and indicate the underlying cause in more detail.
103 The errno global variable will be used to obtain the error value to be
105 decoded.
106 message The location in which to store the returned message. If a suit‐
108 able message return buffer is supplied, this function is thread
109 safe.
110 message_size
112 The size in bytes of the location in which to store the
113 returned message.
114 data The original data, exactly as passed to the uname(2) system
116 call.
117 Example: This function is intended to be used in a fashion similar to
119 the following example:
120 if (uname(data) < 0)
121 {
122 char message[3000];
123 explain_message_uname(message, sizeof(message), data);
124 fprintf(stderr, "%s\n", message);
125 exit(EXIT_FAILURE);
126 }
127 The above code example is available pre-packaged as the
129 explain_uname_or_die(3) function.
130 explain_message_errno_uname
132 void explain_message_errno_uname(char *message, int message_size, int
133 errnum, struct utsname *data);
134 The explain_message_errno_uname function is used to obtain an explana‐
136 tion of an error returned by the uname(2) system call. The least the
137 message will contain is the value of strerror(errno), but usually it
138 will do much better, and indicate the underlying cause in more detail.
139 message The location in which to store the returned message. If a suit‐
141 able message return buffer is supplied, this function is thread
142 safe.
143 message_size
145 The size in bytes of the location in which to store the
146 returned message.
147 errnum The error value to be decoded, usually obtained from the errno
149 global variable just before this function is called. This is
150 necessary if you need to call any code between the system call
151 to be explained and this function, because many libc functions
152 will alter the value of errno.
153 data The original data, exactly as passed to the uname(2) system
155 call.
156 Example: This function is intended to be used in a fashion similar to
158 the following example:
159 if (uname(data) < 0)
160 {
161 int err = errno;
162 char message[3000];
163 explain_message_errno_uname(message, sizeof(message), err,
164 data);
165 fprintf(stderr, "%s\n", message);
166 exit(EXIT_FAILURE);
167 }
168 The above code example is available pre-packaged as the
170 explain_uname_or_die(3) function.
171
173 uname(2)
174 get name and information about current kernel
175 explain_uname_or_die(3)
177 get name and information about current kernel and report errors
178
180 libexplain version 1.4
181 Copyright (C) 2013 Peter Miller
182 explain_uname(3)