02-19-2008
Hehehe..actually I do not understand when should we decide that server is heavy utilization or not. From what I believe and understand, since the CPU LOAD average is still not reach 100%, the server is still considered ok. Hopefully you can help to expalin on how to decide that server is heavy utilize or not. Thank you...
9 More Discussions You Might Find Interesting
1. OS X (Apple)
We have just added 5 macs to what used to be an all Windows shop. Everything works great except the macs upload to a windows 200 file server extremly slow. Are there any suggestions to make the upload faster? (2 Replies)
Discussion started by: wbeard6142
2 Replies
2. SCO
Hi,
Wonder is someone can help.
I've got a server SCO_SV 3.2v5.0.7 PentIII that is located at a different site and is running slow and has been for a week. I've been speaking to a third party who say nothing is wrong with it but its still running slow.
The 3rd party advise it could be a... (2 Replies)
Discussion started by: tez
2 Replies
3. Post Here to Contact Site Administrators and Moderators
Hi Guys,
Since last 20-30 min Server was Too slow ..even few of times i got Database connection error.
Thanks
Sanjay Tripathi (0 Replies)
Discussion started by: SanjayLinux
0 Replies
4. UNIX for Advanced & Expert Users
Hello,
I am using Redhat redhat 4 update 4 kernal 2.6. My server is some time suddenly running slow.
The averge cpu load goes up to 50 to 60. (There is only two CPU and usually, the averge load
is between 1 to 2.5) That time, i see, there are several sessions connected.
Normally, we have... (5 Replies)
Discussion started by: govindts
5 Replies
5. UNIX for Dummies Questions & Answers
Hi,
Following my last post I've mounted the remote server on my local server. However copying files from this mounted server is increadbily slow. If I copy files using rcp it's very fast so I assume there must be a setting somewhere?
Any help appreicated.
Thanks (2 Replies)
Discussion started by: AngryBunny
2 Replies
6. UNIX for Dummies Questions & Answers
Hi guyes our linux server is very slow today and load average is more than 16 .I m new in linux request you to kindly help resolving the issue.
Where can i find the log for the cause.
# lsb_release -a
LSB Version: ... (2 Replies)
Discussion started by: pinga123
2 Replies
7. Solaris
I recently configured a WANBoot server on a Ldom 2.0 running Solaris10u9 with ZFS root. When i start the installation form the client with
Ok Boot net - install ,
it takes at least 20-25 minutes just to download the miniroot on the client .. i read there was a bug on T servers firmware... (2 Replies)
Discussion started by: fugitive
2 Replies
8. Infrastructure Monitoring
There is a big problem with the server (VPS based on OpenVZ, CentOS 5, 3GB RAM). The problem is the following. The first 15-20 minutes after starting the server is operating normally, the load average is less than or about 1.0, but then begins to increase sharply% wa, then hovers around 95-99%.... (2 Replies)
Discussion started by: draiphod
2 Replies
9. AIX
Hello,
All the commands on AIX are running very slow.
Below is few stats but I didn't find any issue in cpu or memory reosurces
vmstat
System configuration: lcpu=4 mem=6144MB ent=1.00
kthr memory page faults cpu
----- -----------... (2 Replies)
Discussion started by: Vishal_dba
2 Replies
LEARN ABOUT MOJAVE
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)