Sponsored Content
Full Discussion: ipcs -m displaying empty
Operating Systems AIX ipcs -m displaying empty Post 302408255 by ashokd001 on Monday 29th of March 2010 03:25:42 AM
Old 03-29-2010
Hi,

* My system is 64 bit.

* linit is set to unlimited.

* setenv EXTSHM=on (EXTSHM is enables with on)

* where to check that is has written any error report ?

* Output of,
>oslevel -s
>5300-04-00
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

ipcs command

Does anyone know how to set the variables with the ipcs command? I need to set the following variables: Shared memory segments message queues semaphore arrays all of these (1 Reply)
Discussion started by: Deuce
1 Replies

2. Programming

System V and POSIX IPCs

I am using SUN 0S 5.7. My application has a dozen programs running in this machine, each instance of a program having 2 POSIX message queues for itself. Totally around 90 POSIX message queues. Another small application uses a SYSTEM V shared memory and a message queue. We face a problem... (1 Reply)
Discussion started by: Deepa
1 Replies

3. Programming

ipcs shows no result in cygwin

Hi, With reference to the thread below: https://www.unix.com/showthread.php?s=&threadid=13247 I have the same program on Cygwin ( unfortuantely win ;( ) My program runs ( offcourse with undesired output) The semget does not give any error, tho I have trapped in case if there is one.... (0 Replies)
Discussion started by: linuxpenguin
0 Replies

4. AIX

ipcs command with out output

hello i'm running on aix 5300-08-02-0822 hacmp 4 when i run ipcs command there is nio output. some one got this problem? best regards ariec (1 Reply)
Discussion started by: ariec
1 Replies

5. Solaris

ipcs Help

hi, I need help with ipcs command on Solaris. What does it do and what are options b,m,o,q does. Here is the sample output of ipcs -oq and ipcs -bm IPC status from <running system> as of Sun Sep 7 23:07:59 GMT 2008 T ID KEY MODE OWNER GROUP CBYTES QNUM... (4 Replies)
Discussion started by: krabu
4 Replies

6. UNIX for Advanced & Expert Users

Question on output of ipcs command

Hi, I read the ipcs man page and am still very confused. Basically, I just want to know whether the output from the ipcs command below means these are the current "TOTAL" memory usage in bytes on the server? Is this correct? Thanks in advance. ipcs command output below: # ipcs... (2 Replies)
Discussion started by: newbie_01
2 Replies

7. Solaris

IPCS COUNT clear

How to clear IPCS queue count in server? (2 Replies)
Discussion started by: Arasu123
2 Replies

8. Solaris

8 character limit for ipcs command , any way to increase # of chars ?

Hello All, We have a working script which identifies and kills ipcs resources which havent been correctly killed during normal shutdowns. It is working fine and dandy however there are some issues now. Environment: SunOS 5.10 Generic_148888-03 sun4u sparc SUNW,SPARC-Enterprise ... (4 Replies)
Discussion started by: icalderus
4 Replies

9. UNIX for Advanced & Expert Users

Ipcs do not show MODE

The ipcs -q command output includes a MODE column which tells user if the process is waiting on read or write on the queue. I used this in scripts on many systems (Solaris, AIX, SCO) a snippet from man MODE (all) The facility access modes and flags: The mode consists of 11... (2 Replies)
Discussion started by: migurus
2 Replies

10. UNIX for Advanced & Expert Users

How to relate ipcs id or cpid to process?

Hi, we have multiple database instances running on solaris server like db1, db2 and db3. Below shown ipcs -pmb shared memory segment output. Using cpid value I want to relate to the database instances db1, db2 and db3. Please let me know how to do this? $ ipcs -pmb IPC status from <running... (9 Replies)
Discussion started by: baladelaware73
9 Replies
explain_setenv(3)					     Library Functions Manual						 explain_setenv(3)

NAME
explain_setenv - explain setenv(3) errors SYNOPSIS
#include <libexplain/setenv.h> const char *explain_setenv(const char *name, const char *value, int overwrite); const char *explain_errno_setenv(int errnum, const char *name, const char *value, int overwrite); void explain_message_setenv(char *message, int message_size, const char *name, const char *value, int overwrite); void explain_message_errno_setenv(char *message, int message_size, int errnum, const char *name, const char *value, int overwrite); DESCRIPTION
These functions may be used to obtain explanations for errors returned by the setenv(3) system call. explain_setenv const char *explain_setenv(const char *name, const char *value, int overwrite); The explain_setenv function is used to obtain an explanation of an error returned by the setenv(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. name The original name, exactly as passed to the setenv(3) system call. value The original value, exactly as passed to the setenv(3) system call. overwrite The original overwrite, exactly as passed to the setenv(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. Example: This function is intended to be used in a fashion similar to the following example: if (setenv(name, value, overwrite) < 0) { fprintf(stderr, "%s ", explain_setenv(name, value, overwrite)); exit(EXIT_FAILURE); } The above code example is available pre-packaged as the explain_setenv_or_die(3) function. explain_errno_setenv const char *explain_errno_setenv(int errnum, const char *name, const char *value, int overwrite); The explain_errno_setenv function is used to obtain an explanation of an error returned by the setenv(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. 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. name The original name, exactly as passed to the setenv(3) system call. value The original value, exactly as passed to the setenv(3) system call. overwrite The original overwrite, exactly as passed to the setenv(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. Example: This function is intended to be used in a fashion similar to the following example: if (setenv(name, value, overwrite) < 0) { int err = errno; fprintf(stderr, "%s ", explain_errno_setenv(err, name, value, overwrite)); exit(EXIT_FAILURE); } The above code example is available pre-packaged as the explain_setenv_or_die(3) function. explain_message_setenv void explain_message_setenv(char *message, int message_size, const char *name, const char *value, int overwrite); The explain_message_setenv function is used to obtain an explanation of an error returned by the setenv(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. 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. name The original name, exactly as passed to the setenv(3) system call. value The original value, exactly as passed to the setenv(3) system call. overwrite The original overwrite, exactly as passed to the setenv(3) system call. Example: This function is intended to be used in a fashion similar to the following example: if (setenv(name, value, overwrite) < 0) { char message[3000]; explain_message_setenv(message, sizeof(message), name, value, overwrite); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } The above code example is available pre-packaged as the explain_setenv_or_die(3) function. explain_message_errno_setenv void explain_message_errno_setenv(char *message, int message_size, int errnum, const char *name, const char *value, int overwrite); The explain_message_errno_setenv function is used to obtain an explanation of an error returned by the setenv(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. name The original name, exactly as passed to the setenv(3) system call. value The original value, exactly as passed to the setenv(3) system call. overwrite The original overwrite, exactly as passed to the setenv(3) system call. Example: This function is intended to be used in a fashion similar to the following example: if (setenv(name, value, overwrite) < 0) { int err = errno; char message[3000]; explain_message_errno_setenv(message, sizeof(message), err, name, value, overwrite); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } The above code example is available pre-packaged as the explain_setenv_or_die(3) function. SEE ALSO
setenv(3) change or add an environment variable explain_setenv_or_die(3) change or add an environment variable and report errors COPYRIGHT
libexplain version 0.52 Copyright (C) 2010 Peter Miller explain_setenv(3)
All times are GMT -4. The time now is 02:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy