06-30-2014
Thanks Makarand... I will try the same.
Corona688---the message is generated (what i could see) is as because there are some SSL handshake failure and hence the entries in the log file.
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hi....
how i can configurator a log file on real time....on unix solaris....
thanks a lot....
Best Regards... (3 Replies)
Discussion started by: chanfle
3 Replies
2. Shell Programming and Scripting
When I run "/etc/myApp" I am presented with continuous output, just about once per second.
However when I try to get the information in Perl via a piped open, it waits till the end to give me anything... my code:
open (OUTPUT,"/etc/myApp |");
while (<OUTPUT>){
print $_;
}... (2 Replies)
Discussion started by: jjinno
2 Replies
3. Shell Programming and Scripting
Hi all,
i would like to write the shell script program, it can monitor the access_log "real time"
when the access_log writing the line contain "abcdef" the program will be "COPY" this line into a file named "abcdef.txt", do the same thing if the contain "123456" "COPY" it into a file named... (3 Replies)
Discussion started by: eric_wong_ch
3 Replies
4. HP-UX
Hey all, I have a problem I was hoping to get some help on. So I have my two auditfiles, audfile1 and audfile2 that can be written to, I want to have the text version of them write to an NFS mount that I have set up. So i already know that i can do .secure/etc/audsp audfile1 > //nfsmount/folder/... (5 Replies)
Discussion started by: CleverRiver6
5 Replies
5. Shell Programming and Scripting
Hi people
I have a bash script with a line like this:
python example.py >> log &
But i can't see anything in the log file while python program is running only if the program ends seems to write the log file.
"$ cat log" for example don't show anything until the program ends.
Is there... (4 Replies)
Discussion started by: Tieso
4 Replies
6. UNIX for Advanced & Expert Users
Hello All,
I am building a real time parser for a log file in my application.
The log file is continuously written at a very fast pace and gets rolled over every 10 minutes.
I have measured the speed and observed that around 1000 lines are written to it every second, each line about 30-40... (7 Replies)
Discussion started by: cool.aquarian
7 Replies
7. Shell Programming and Scripting
Below is my script to log all the command input by any user to /var/log/messages. But I cant achieve the desired output that i want. PLease see below.
function log2syslog
{
declare COMMAND
COMMAND=$(fc -ln -0)
logger -p local1.notice -t bash -i -- "$USER:$COMMAND"
}
trap... (12 Replies)
Discussion started by: invinzin21
12 Replies
LEARN ABOUT PLAN9
ssl_connect
SSL_connect(3SSL) OpenSSL SSL_connect(3SSL)
NAME
SSL_connect - initiate the TLS/SSL handshake with an TLS/SSL server
SYNOPSIS
#include <openssl/ssl.h>
int SSL_connect(SSL *ssl);
DESCRIPTION
SSL_connect() initiates the TLS/SSL handshake with a server. The communication channel must already have been set and assigned to the ssl
by setting an underlying BIO.
NOTES
The behaviour of SSL_connect() depends on the underlying BIO.
If the underlying BIO is blocking, SSL_connect() will only return once the handshake has been finished or an error occurred.
If the underlying BIO is non-blocking, SSL_connect() will also return when the underlying BIO could not satisfy the needs of SSL_connect()
to continue the handshake, indicating the problem by the return value -1. In this case a call to SSL_get_error() with the return value of
SSL_connect() will yield SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE. The calling process then must repeat the call after taking
appropriate action to satisfy the needs of SSL_connect(). The action depends on the underlying BIO. When using a non-blocking socket,
nothing is to be done, but select() can be used to check for the required condition. When using a buffering BIO, like a BIO pair, data must
be written into or retrieved out of the BIO before being able to continue.
RETURN VALUES
The following return values can occur:
<0 The TLS/SSL handshake was not successful, because a fatal error occurred either at the protocol level or a connection failure occurred.
The shutdown was not clean. It can also occur of action is need to continue the operation for non-blocking BIOs. Call SSL_get_error()
with the return value ret to find out the reason.
0 The TLS/SSL handshake was not successful but was shut down controlled and by the specifications of the TLS/SSL protocol. Call
SSL_get_error() with the return value ret to find out the reason.
1 The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been established.
SEE ALSO
SSL_get_error(3), SSL_accept(3), SSL_shutdown(3), ssl(3), bio(3), SSL_set_connect_state(3), SSL_do_handshake(3), SSL_CTX_new(3)
1.0.1e 2014-08-06 SSL_connect(3SSL)