09-02-2014
yes
this is the value of net.ipv4.tcp_keepalive_intvl = 75
and my OS support nohup .
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
hello to everyone, i was wondering if you could help me with a script im working on, it's kind of simple but i dont have a lot experience on unix comands: well, here it is:
you might apreciate the infinite while loop :D, it is supossed to be running on the server all day scaning it every 5... (12 Replies)
Discussion started by: sx3v1l_1n51de
12 Replies
2. UNIX for Dummies Questions & Answers
Hi Everybody
I have small requirement that needs to be implemented in shell script.
Currently i have shell script which invokes a java process say "Process A" which runs in background.
If some one tries to invoke again the same shell script , then there should be some mechanism inside the... (23 Replies)
Discussion started by: appleforme1415
23 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I'm investigate about a problem regarding a connection between two server (S1 and S2).
A client software on S1 made a pool of connections on S2; for some reason some connections end but sockets still alive on S2 and not on S1.
I always knew about sockets as a pair of processes; is it... (1 Reply)
Discussion started by: grado
1 Replies
4. Shell Programming and Scripting
Hi
I want to keep my script running even when i am logged off from the box.
can we run the script in background which can automatically run every hour?
Please advise.
Thank you (1 Reply)
Discussion started by: Prateek007
1 Replies
5. Solaris
Hi everyone,
I am hoping anyone of you could help me in this weird problem we have in 1 of our Solaris 10 servers. Lately, we have been having some ftp problems in this server. Though it can ping any server within the network, it seems that it can only ftp to a select few. For most servers, the... (4 Replies)
Discussion started by: labdakos
4 Replies
6. UNIX for Dummies Questions & Answers
How to write a shell script to find ports are open for the server.
Thanks in advance.
regards
krackjack (4 Replies)
Discussion started by: krackjack
4 Replies
7. Solaris
Hello guys, I have one script running that I need to keep it running 24x7 so I'd like to know how can I implement a sort of monitoring process I mean if for some reason this process dies somehow it gets automatically started again.
Thanks. (8 Replies)
Discussion started by: cerioni
8 Replies
8. What is on Your Mind?
Odd thing.
I posted in the Solaris forum, new user, just asking for a bit of advice. Nothing too complicated. As of this post there have been 140 views and zero replies. So that got me thinking, is this normal? I had a look around, and I see the same thing on many other threads, and in other... (2 Replies)
Discussion started by: _JonB_
2 Replies
9. Programming
Hi
I'm adding http 1.1 GET to my project and trying to use “Keep-Alive” HTTP connections to the host, The problem is when I recv() the first page, it succeeds. However, the 2nd consecutive recv() will receive zero bytes, for which I really have no idea. As per HTTP 1.1 I have Connection: ... (6 Replies)
Discussion started by: Projecteer
6 Replies
NOHUP(1) BSD General Commands Manual NOHUP(1)
NAME
nohup -- invoke a command immune to hangups
SYNOPSIS
nohup utility [arg ...]
DESCRIPTION
The nohup command allows the specified utility to be protected from termination if the user should become logged out (for example, due to a
modem line or TCP/IP connection being dropped). To do this, nohup sets the SIGHUP signal(3) (``terminal line hangup'') to be ignored, then
executes utility along with any arguments.
If the standard output is a terminal, the standard output is appended to the file nohup.out in the current directory. If standard error is a
terminal, it is directed to the same place as the standard output. If the output file nohup.out cannot be created in the current directory,
nohup attempts to create the file in the user's home directory. If the file nohup.out cannot be created, either in the current directory or
the user's home directory, nohup will exit without invoking utility, with an exit value as described below.
ENVIRONMENT
The following variable is used by nohup.
HOME User's home directory.
EXIT STATUS
The nohup utility exits with one of the following values:
126 The utility was found but could not be invoked.
127 The utility could not be found or an error occurred in nohup.
Otherwise, the exit status of nohup will be that of utility.
SEE ALSO
signal(3)
STANDARDS
The nohup command is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
BSD
July 15, 2005 BSD