This is an odd thing to do. But I just got this script to work:
One of my sleep processes represents a process that might run too long. The other sleep process is the timer. Either process could play either role, but I envisioned that first line as the timer and the second as the process to be timed. One of the processes will probably finish first and then run the "kill -term -$$". This will kill the process group. On a multiprocessor system simultaneous kills may occur, but the kernel will ensure that they happen serially. There is no race condition here. This depends on the shell putting all processes in a script into a single process group. So neither sleep process could be replaced with another shell script because it would become a new process group.
I am currently running SCO OpenServer.
When the machine is restart it automatically intitiates processes that allow me to use the ARCserv backup software... Recently, these process were killed and I would like to restart them. The problem is I dont know the name or location of the files invoked... (1 Reply)
Is there a way to monitor certain processes and if they hang too long to kill them, but certain scripts which are expected to take a long time to let them go?
Thank you
Richard (4 Replies)
I have a RHEL 2.1 machine that I am trying to get to mount a remote nfs filesystem. Both servers have 2 network interfaces. My linux machine can mount the filesystem through one interface with no problems but if I switch over and try to mount it through the other interface using a totally... (1 Reply)
Hi
Is there an easy way to identify and group currently running processes into OS processes and APP processes. Not all applications are installed as packages.
Any free tools or scripts to do this?
Many thanks. (2 Replies)
Hello - We have setup printers to startup in the /etc/rc.d/8 directory and when the SCO system is booted this script should kick them off or start them up but it doesn't. So I have to start it from root and leave the window open. I know this isn't right and trying to figure out what's missing. ... (13 Replies)
Hello,
I'm having a problem starting the cron daemon automatically from inittab, let me provide the details below:
We are having five equally installed machines. One of them was upgraded in the past, one we upgraded recently, both from 5300-05-06 to 5300-07-01-0748. On the upgraded... (6 Replies)
I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time.
Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
e.g.
File name: File.txt
cat File.txt
Result:
#INBOUND_QUEUE=FAQ1
INBOUND_QUEUE=FAQ2
I want to get the value for one which is not commented out.
Thanks, (3 Replies)
Discussion started by: Tanu
3 Replies
LEARN ABOUT CENTOS
ssl_ctx_set_timeout
SSL_CTX_set_timeout(3) OpenSSL SSL_CTX_set_timeout(3)NAME
SSL_CTX_set_timeout, SSL_CTX_get_timeout - manipulate timeout values for session caching
SYNOPSIS
#include <openssl/ssl.h>
long SSL_CTX_set_timeout(SSL_CTX *ctx, long t);
long SSL_CTX_get_timeout(SSL_CTX *ctx);
DESCRIPTION
SSL_CTX_set_timeout() sets the timeout for newly created sessions for ctx to t. The timeout value t must be given in seconds.
SSL_CTX_get_timeout() returns the currently set timeout value for ctx.
NOTES
Whenever a new session is created, it is assigned a maximum lifetime. This lifetime is specified by storing the creation time of the
session and the timeout value valid at this time. If the actual time is later than creation time plus timeout, the session is not reused.
Due to this realization, all sessions behave according to the timeout value valid at the time of the session negotiation. Changes of the
timeout value do not affect already established sessions.
The expiration time of a single session can be modified using the SSL_SESSION_get_time(3) family of functions.
Expired sessions are removed from the internal session cache, whenever SSL_CTX_flush_sessions(3) is called, either directly by the
application or automatically (see SSL_CTX_set_session_cache_mode(3))
The default value for session timeout is decided on a per protocol basis, see SSL_get_default_timeout(3). All currently supported
protocols have the same default timeout value of 300 seconds.
RETURN VALUES
SSL_CTX_set_timeout() returns the previously set timeout value.
SSL_CTX_get_timeout() returns the currently set timeout value.
SEE ALSO ssl(3), SSL_CTX_set_session_cache_mode(3), SSL_SESSION_get_time(3), SSL_CTX_flush_sessions(3), SSL_get_default_timeout(3)1.0.1e 2013-02-11 SSL_CTX_set_timeout(3)