Sponsored Content
Full Discussion: ldap recovery
Operating Systems Linux Red Hat ldap recovery Post 302510958 by Corona688 on Tuesday 5th of April 2011 11:17:42 AM
Old 04-05-2011
Crashes in what fashion? More detail is needed.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

help for db password recovery

hi,all my database (.db) is created by sysbase adaptive server anywhere7.0 ! the user id is DBA. but I lost the password . Could you recovery the passwrod of this db file? thanks ! iwind (1 Reply)
Discussion started by: northwind
1 Replies

2. Programming

C Code recovery

Hai, Is there any tool available to get back the C code from an executable file in solaris. Accidentally the program was deleted by somebody. We need to recover the code since it has to be implemented on another system. I copied that executable and tried to execute it on another solaris machine.... (2 Replies)
Discussion started by: smvel
2 Replies

3. Solaris

Disaster Recovery

Recovering Solaris to an alternate server I was just wondering if anyone could give me some points on restoring a Solaris 9 backup to an alternate server. Basically, we use netbackup 6 and I was wondering what the best procedures are for doing this? What things do we need to take into... (3 Replies)
Discussion started by: aaron2k
3 Replies

4. AIX

System recovery

Hi everyone I'm green AIX user or rather beginner (light green). Unfortunately I have to restore my system + data from scratch (things happen) and make it up and running. I've never done it before. Can someone of you provide me with link/procedure/instruction how to do it? Now I know only:... (3 Replies)
Discussion started by: fraydey
3 Replies

5. Solaris

Solaris recovery

Some thing happened to our solaris 10 ( sparc ) box and it is not coming up now. These are some of the console messages : I assume it is not able to find very basic system libraries so i need to tell it some how to find it under /lib:/usr/lib. I booted it from the CD but now i... (4 Replies)
Discussion started by: rajwinder
4 Replies

6. UNIX for Advanced & Expert Users

something like LDAP Administrator 2011.1 "LDAP-SQL" but for the CLI

Hi I am searching a tool like "LDAP Administrator 2011.1"/ "LDAP-SQL" but for the CLI. Wish to use LDAP-SQL in scripts (non Windows GUI environment) http://ldapadministrator.com/resources/english/2011.1/images/sqlquery_large.png Softerra LDAP Administrator 2011.1 - What's New OS is... (2 Replies)
Discussion started by: slashdotweenie
2 Replies

7. Red Hat

Please: help to recovery boot with new vg

The situation: i try to boot centos in new environement(the vg name is changed) i edit the menu.lst of grub,did grub-install,then mkinitrd `uname -r`.img `uname -r` but when i reboot the new vg is not find and i obtain only a kernel panic :( (0 Replies)
Discussion started by: Linusolaradm1
0 Replies

8. Red Hat

Disaster Recovery

Hi, I just want to throw something out there for opinions and viewpoints relating to a Disaster Recovery site. Besides the live production environment, do you think a DR environment should include: - pre-production environment - QA Environment ......or would this be considered to be OTT... (3 Replies)
Discussion started by: Duffs22
3 Replies

9. Solaris

Solaris 11 recovery

Hi, I need to recover the Solaris 11 OS, and it backup via Netbackup 7.6 file level backup only. Does anyone know what are steps to recover it? Thanks. :confused::confused::confused: (3 Replies)
Discussion started by: freshmeat
3 Replies

10. Solaris

LDAP Client not connecting to LDAP server

I have very limited knowledge on LDAP configuration and have been trying fix one issue, but unsuccessful. The server, I am working on, is Solaris-10 zone. sudoers is configured on LDAP (its not on local server). I have access to login directly on server with root, but somehow sudo is not working... (9 Replies)
Discussion started by: solaris_1977
9 Replies
explain_wait(3) 					     Library Functions Manual						   explain_wait(3)

NAME
explain_wait - explain wait(2) errors SYNOPSIS
#include <libexplain/wait.h> const char *explain_wait(int *status); const char *explain_errno_wait(int errnum, int *status); void explain_message_wait(char *message, int message_size, int *status); void explain_message_errno_wait(char *message, int message_size, int errnum, int *status); DESCRIPTION
These functions may be used to obtain explanations for errors returned by the wait(2) system call. explain_wait const char *explain_wait(int *status); The explain_wait function is used to obtain an explanation of an error returned by the wait(2) 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 (wait(status) < 0) { fprintf(stderr, "%s ", explain_wait(status)); exit(EXIT_FAILURE); } status The original status, exactly as passed to the wait(2) 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_wait const char *explain_errno_wait(int errnum, int *status); The explain_errno_wait function is used to obtain an explanation of an error returned by the wait(2) 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 (wait(status) < 0) { int err = errno; fprintf(stderr, "%s ", explain_errno_wait(err, status)); exit(EXIT_FAILURE); } 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. status The original status, exactly as passed to the wait(2) 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_wait void explain_message_wait(char *message, int message_size, int *status); The explain_message_wait function may be used to obtain an explanation of an error returned by the wait(2) 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 (wait(status) < 0) { char message[3000]; explain_message_wait(message, sizeof(message), status); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } 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. status The original status, exactly as passed to the wait(2) system call. explain_message_errno_wait void explain_message_errno_wait(char *message, int message_size, int errnum, int *status); The explain_message_errno_wait function may be used to obtain an explanation of an error returned by the wait(2) 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 (wait(status) < 0) { int err = errno; char message[3000]; explain_message_errno_wait(message, sizeof(message), err, status); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } 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. status The original status, exactly as passed to the wait(2) system call. SEE ALSO
wait(2) wait for process to change state explain_wait_or_die(3) wait for process to change state and report errors COPYRIGHT
libexplain version 0.52 Copyright (C) 2008 Peter Miller explain_wait(3)
All times are GMT -4. The time now is 10:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy