01-24-2008
Well, for example the V440 has ROHS compliant and non-compliant versions as well. I'm trying to determine which of those we own.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hi guys,
need some help on this error message.
im running solaris 2.6 on a e3500 and lately i encountered this error:-
lp: Warning: Received SIGPIPE; continuing
last message repeated 1 time
Multiple Softerrors:
2 Intermittent, 4 Persistent, and 0 Sticky Softerrors accumulated
from... (4 Replies)
Discussion started by: giriplug
4 Replies
2. Solaris
Hi boss,
i want to purches one second hand system intel P3 for practice.vender having mercury mother board.it will support sun 9 or 10. if any problem will create while configure like (ex:-apache) .tell me which configuration (intel) is best for practice.In intel system what are the... (2 Replies)
Discussion started by: rjay.com
2 Replies
3. UNIX for Advanced & Expert Users
Hi,
I am new to this forum and hope someone can help. Does anyone know how to restore a Solaris 9 backup tape from server A to a completely different server B hardware. Both boxes are sun 64bit.
Your help is much appreciated.
Thank you
Jan. (5 Replies)
Discussion started by: snerta
5 Replies
4. What is on Your Mind?
I am just curious. How is RoHS compliancy impacting IT? I understand it is addressing environmental concerns but what are other impacts (positive/negative) if any? Does this impact tax liability somehow? (1 Reply)
Discussion started by: mhm4
1 Replies
5. Solaris
Hi,
I'm trying to determine which HBA cards are installed on my Solaris 10 (Sun-Fire-V240) machine.
The relevant data I have is below, but from it I cannot ascertain for sure if I have Emulex 10000 or 11000 HBA cards.
Can anyone suggest how to determine my HBA hardware ?
Thanks,
Ron.
... (4 Replies)
Discussion started by: ronbarak
4 Replies
6. Solaris
hi :),
i am new to this forum and i am in need of some help. one of my friend i having a Sun Ultra 2 UPA/Sbus (UltraSPARC-II 296Mhz) 640 MB ram. i am not sure if that configuration will be helpful to try out some sysadmin commands. this machine has a 21-inch monster monitor, which i think... (5 Replies)
Discussion started by: sudhiroracle
5 Replies
7. UNIX for Advanced & Expert Users
Hello,
Im working on solaris 9 and I need to write script which monitoring
several hardware componenets for any failures such as memory , Disks , power supply etc.
I using prtdiag to extract this info.
What should I check in the output for :
Memory (Is the block of "Memory Module Groups"... (1 Reply)
Discussion started by: Alalush
1 Replies
8. Solaris
Hi ...
i am new about HP -Solaris 10 x86
I have fresh hardware, I need to check the
RAM , CPU, BUS , Hard drives mounted
Can you please help me with commnds.
Thanks in advance (3 Replies)
Discussion started by: anand87
3 Replies
9. Hardware
hi
does an RoHS V890 server accept components (I/O board , motherboard, CPU/MEMORY modules) from non-RoHS V890 severs ??? because they have different part numbers
thnx (3 Replies)
Discussion started by: bahjatm
3 Replies
10. Solaris
Hello Everyone,
I'm new to Solaris, less than a week to give an idea how green I am.:eek: Although new to UNIX, I've been running Linux (i.e. OpenSUSE, Ultimate Edition, Arch, and obviously Ubuntu) for many years, so, I decided to put Solaris 11 on my 12 core opteron. I had a bit of difficulty... (23 Replies)
Discussion started by: Nostradamus1973
23 Replies
LEARN ABOUT LINUX
strerror
STRERROR(3) Linux Programmer's Manual STRERROR(3)
NAME
strerror, strerror_r - return string describing error number
SYNOPSIS
#include <string.h>
char *strerror(int errnum);
int strerror_r(int errnum, char *buf, size_t buflen);
/* XSI-compliant */
char *strerror_r(int errnum, char *buf, size_t buflen);
/* GNU-specific */
Feature Test Macro Requirements for glibc (see feature_test_macros(7)):
The XSI-compliant version of strerror_r() is provided if:
(_POSIX_C_SOURCE >= 200112L || _XOPEN_SOURCE >= 600) && ! _GNU_SOURCE
Otherwise, the GNU-specific version is provided.
DESCRIPTION
The strerror() function returns a pointer to a string that describes the error code passed in the argument errnum, possibly using the
LC_MESSAGES part of the current locale to select the appropriate language. This string must not be modified by the application, but may be
modified by a subsequent call to perror(3) or strerror(). No library function will modify this string.
The strerror_r() function is similar to strerror(), but is thread safe. This function is available in two versions: an XSI-compliant ver-
sion specified in POSIX.1-2001 (available since glibc 2.3.4), and a GNU-specific version (available since glibc 2.0). The XSI-compliant
version is provided with the feature test macros settings shown in the SYNOPSIS; otherwise the GNU-specific version is provided. If no
feature test macros are explicitly defined, then (since glibc 2.4) _POSIX_SOURCE is defined by default with the value 200112L, so that the
XSI-compliant version of strerror_r() is provided by default.
The XSI-compliant strerror_r() is preferred for portable applications. It returns the error string in the user-supplied buffer buf of
length buflen.
The GNU-specific strerror_r() returns a pointer to a string containing the error message. This may be either a pointer to a string that
the function stores in buf, or a pointer to some (immutable) static string (in which case buf is unused). If the function stores a string
in buf, then at most buflen bytes are stored (the string may be truncated if buflen is too small) and the string always includes a termi-
nating null byte.
RETURN VALUE
The strerror() and the GNU-specific strerror_r() functions return the appropriate error description string, or an "Unknown error nnn" mes-
sage if the error number is unknown.
The XSI-compliant strerror_r() function returns 0 on success; on error, -1 is returned and errno is set to indicate the error.
ERRORS
EINVAL The value of errnum is not a valid error number.
ERANGE Insufficient storage was supplied to contain the error description string.
CONFORMING TO
strerror() is specified by POSIX.1-2001, C89, C99. strerror_r() is specified by POSIX.1-2001.
The GNU-specific strerror_r() function is a nonstandard extension.
POSIX.1-2001 permits strerror() to set errno if the call encounters an error, but does not specify what value should be returned as the
function result in the event of an error. On some systems, strerror() returns NULL if the error number is unknown. On other systems, str-
error() returns a string something like "Error nnn occurred" and sets errno to EINVAL if the error number is unknown.
SEE ALSO
err(3), errno(3), error(3), perror(3), strsignal(3)
COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
2009-03-30 STRERROR(3)