09-10-2008
They seem perfectly good to me.
Maybe if you described exactly which part you don't understand we might be able to help you.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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
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
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
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. AIX
I am trying to run myApplication which allocates Some amount of shared memory at startup.
It failed because not available shared memory are available.
But when i ran,
ipcs -m
it is displaying empty(i.e no shared memory allocated in system.)
Why "ipcs -m" is displaying empty ?
... (5 Replies)
Discussion started by: ashokd001
5 Replies
6. UNIX for Advanced & Expert Users
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
How to clear IPCS queue count in server? (2 Replies)
Discussion started by: Arasu123
2 Replies
8. Solaris
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
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
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
LEARN ABOUT PLAN9
ssl_ctx_new
SSL_CTX_new(3SSL) OpenSSL SSL_CTX_new(3SSL)
NAME
SSL_CTX_new - create a new SSL_CTX object as framework for TLS/SSL enabled functions
SYNOPSIS
#include <openssl/ssl.h>
SSL_CTX *SSL_CTX_new(const SSL_METHOD *method);
DESCRIPTION
SSL_CTX_new() creates a new SSL_CTX object as framework to establish TLS/SSL enabled connections.
NOTES
The SSL_CTX object uses method as connection method. The methods exist in a generic type (for client and server use), a server only type,
and a client only type. method can be of the following types:
SSLv2_method(void), SSLv2_server_method(void), SSLv2_client_method(void)
A TLS/SSL connection established with these methods will only understand the SSLv2 protocol. A client will send out SSLv2 client hello
messages and will also indicate that it only understand SSLv2. A server will only understand SSLv2 client hello messages.
SSLv3_method(void), SSLv3_server_method(void), SSLv3_client_method(void)
A TLS/SSL connection established with these methods will only understand the SSLv3 protocol. A client will send out SSLv3 client hello
messages and will indicate that it only understands SSLv3. A server will only understand SSLv3 client hello messages. This especially
means, that it will not understand SSLv2 client hello messages which are widely used for compatibility reasons, see SSLv23_*_method().
TLSv1_method(void), TLSv1_server_method(void), TLSv1_client_method(void)
A TLS/SSL connection established with these methods will only understand the TLSv1 protocol. A client will send out TLSv1 client hello
messages and will indicate that it only understands TLSv1. A server will only understand TLSv1 client hello messages. This especially
means, that it will not understand SSLv2 client hello messages which are widely used for compatibility reasons, see SSLv23_*_method().
It will also not understand SSLv3 client hello messages.
SSLv23_method(void), SSLv23_server_method(void), SSLv23_client_method(void)
A TLS/SSL connection established with these methods will understand the SSLv2, SSLv3, and TLSv1 protocol. A client will send out SSLv2
client hello messages and will indicate that it also understands SSLv3 and TLSv1. A server will understand SSLv2, SSLv3, and TLSv1
client hello messages. This is the best choice when compatibility is a concern.
The list of protocols available can later be limited using the SSL_OP_NO_SSLv2, SSL_OP_NO_SSLv3, SSL_OP_NO_TLSv1 options of the
SSL_CTX_set_options() or SSL_set_options() functions. Using these options it is possible to choose e.g. SSLv23_server_method() and be able
to negotiate with all possible clients, but to only allow newer protocols like SSLv3 or TLSv1.
SSL_CTX_new() initializes the list of ciphers, the session cache setting, the callbacks, the keys and certificates, and the options to its
default values.
RETURN VALUES
The following return values can occur:
NULL
The creation of a new SSL_CTX object failed. Check the error stack to find out the reason.
Pointer to an SSL_CTX object
The return value points to an allocated SSL_CTX object.
SEE ALSO
SSL_CTX_free(3), SSL_accept(3), ssl(3), SSL_set_connect_state(3)
1.0.1e 2013-02-11 SSL_CTX_new(3SSL)