Sponsored Content
Full Discussion: Solaris 10 man pages
Operating Systems Solaris Solaris 10 man pages Post 302092306 by XP_2600 on Sunday 8th of October 2006 08:33:09 PM
Old 10-08-2006
I got similar problem before.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Man pages

Hello , I just installed openssh in my system . I actually tried to man sshd but it says no entry , though there is a man directory in the installation which have the man pages for sshd . Can anyone tell me how should i install these man pages . DP (2 Replies)
Discussion started by: DPAI
2 Replies

2. UNIX for Dummies Questions & Answers

man pages

Hi, I've written now a man pages, but I don't knwo how to get 'man' to view them. Where have I to put this files, which directories are allowed?? THX Bensky (3 Replies)
Discussion started by: bensky
3 Replies

3. UNIX for Dummies Questions & Answers

man pages

When reading man pages, I notice that sometimes commands are follwed by a number enclosed in parenthesis. such as: mkdir calls the mkdir(2) system call. What exactly does this mean? (4 Replies)
Discussion started by: dangral
4 Replies

4. UNIX for Dummies Questions & Answers

Installing man pages on Solaris 10

I am doing some new SOlaris Installs and the man pages do not seem to be included. Do you know how I can add them after the fact? Thanks! Aaron (5 Replies)
Discussion started by: amheck
5 Replies

5. UNIX for Dummies Questions & Answers

Man pages on Solaris 10

Hi, I want to install man pages package from solaris 10. Solaris 10 has already been installed on my servor but I have to add the man pages packages. I search for a long time on internet this package but I didn't find a compatible one... So I downloaded Solaris 10 from Sun site to get this... (1 Reply)
Discussion started by: MasterapocA
1 Replies

6. Solaris

Solaris man pages online

Anybody found where Oracle have hidden the Solaris 10 "man" pages in their new website? My saved links don't work any more. (2 Replies)
Discussion started by: methyl
2 Replies

7. Solaris

MAN PAGES

Hi everyone, I have a small query, in solaris the man pages get displayed on half of the terminal , can i get a full terminal or full screen display ?:) (2 Replies)
Discussion started by: M.Choudhury
2 Replies

8. HP-UX

Looking for some man pages.

Can anyone supply me with the man pages for: omnidatalist omnibarlist omnisap.exe I prefer the source man pages in nroff format. A clue about the software bundles which supply these man pages is fine as well. OS: HP-UX TIA (11 Replies)
Discussion started by: sb008
11 Replies

9. UNIX for Dummies Questions & Answers

gcc man pages not found under Solaris 10

Hi friends, When I try to see the man pages of gcc, man gcc I see No manual entry for gcc. Could you help me please. I am running solaris 10 Thanks! (4 Replies)
Discussion started by: gabam
4 Replies

10. Solaris

Solaris 11 man pages won't show on CLI

Hello guys, I am a newbie. Just freshly installed Solaris 11. When I try to type for example root@t1000:~# man zpool It says bash: man: command not found. It used to show manual pages before installation. Any help is appreciated. Thanks. (5 Replies)
Discussion started by: nazimbilir
5 Replies
explain_ferror(3)					     Library Functions Manual						 explain_ferror(3)

NAME
explain_ferror - explain ferror(3) errors SYNOPSIS
#include <libexplain/ferror.h> const char *explain_ferror(FILE *fp); const char *explain_errno_ferror(int errnum, FILE *fp); void explain_message_ferror(char *message, int message_size, FILE *fp); void explain_message_errno_ferror(char *message, int message_size, int errnum, FILE *fp); DESCRIPTION
These functions may be used to obtain explanations for errors returned by the ferror(3) system call. explain_ferror const char *explain_ferror(FILE *fp); The explain_ferror function is used to obtain an explanation of an error returned by the ferror(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. This function is intended to be used in a fashion similar to the following example: if (ferror(fp) < 0) { fprintf(stderr, "%s ", explain_ferror(fp)); exit(EXIT_FAILURE); } It is essential that this function cal be placed as close as possible to the I/O code that has caused the problem, otherwise intervening code could have altered the errno global variable. fp The original fp, exactly as passed to the ferror(3) system call. 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. explain_errno_ferror const char *explain_errno_ferror(int errnum, FILE *fp); The explain_errno_ferror function is used to obtain an explanation of an error returned by the ferror(3) system call. The least the mes- sage will contain is the value of strerror(errnum), but usually it will do much better, and indicate the underlying cause in more detail. This function is intended to be used in a fashion similar to the following example: if (ferror(fp) < 0) { int err = errno; fprintf(stderr, "%s ", explain_errno_ferror(err, fp)); exit(EXIT_FAILURE); } It is essential that this function cal be placed as close as possible to the I/O code that has caused the problem, otherwise intervening code could have altered the errno global variable. 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. fp The original fp, exactly as passed to the ferror(3) system call. 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. explain_message_ferror void explain_message_ferror(char *message, int message_size, FILE *fp); The explain_message_ferror function may be used to obtain an explanation of an error returned by the ferror(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. This function is intended to be used in a fashion similar to the following example: if (ferror(fp) < 0) { char message[3000]; explain_message_ferror(message, sizeof(message), fp); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } It is essential that this function cal be placed as close as possible to the I/O code that has caused the problem, otherwise intervening code could have altered the errno global variable. 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. fp The original fp, exactly as passed to the ferror(3) system call. explain_message_errno_ferror void explain_message_errno_ferror(char *message, int message_size, int errnum, FILE *fp); The explain_message_errno_ferror function may be used to obtain an explanation of an error returned by the ferror(3) system call. The least the message will contain is the value of strerror(errnum), but usually it will do much better, and indicate the underlying cause in more detail. This function is intended to be used in a fashion similar to the following example: if (ferror(fp) < 0) { int err = errno; char message[3000]; explain_message_errno_ferror(message, sizeof(message), err, fp); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } It is essential that this function cal be placed as close as possible to the I/O code that has caused the problem, otherwise intervening code could have altered the errno global variable. 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. fp The original fp, exactly as passed to the ferror(3) system call. SEE ALSO
ferror(3) check stream status explain_ferror_or_die(3) check stream status and report errors COPYRIGHT
libexplain version 0.52 Copyright (C) 2008 Peter Miller explain_ferror(3)
All times are GMT -4. The time now is 01:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy