06-23-2005
What happens to the user's background processes? I am assuming if they are not "nohup"ed they will be killed.
10 More Discussions You Might Find Interesting
1. SCO
Hi,
Please let us know of any possiblity of identifying and killing unix proces invoked externally (by an external tool which does not create a session). 'who' command gives idle time of sessions. But what we are looking for is idle time of a process. 'ps' command gives the elapsed/running... (1 Reply)
Discussion started by: vbalajis
1 Replies
2. HP-UX
My max user parm is set to 1050. I'm currently at 1038 this is causing major slow downs on the server. I looking for a way log off "idle" user logins with out having to do it individually. :confused: (5 Replies)
Discussion started by: rfmurphy_6
5 Replies
3. UNIX for Advanced & Expert Users
Im "supporting" at least 2500 HP-UX workstations with CAD-related software with the B.11.11 build. I cant say anymore than that because of my companys sligtly paranoid security policy .
The last few days a new problem has arised from nowhere.
The problem is that users gets logged off when the... (5 Replies)
Discussion started by: Laoinjo
5 Replies
4. Shell Programming and Scripting
I need a script to kill those process id whose idle time is more than 30min
plz help me (3 Replies)
Discussion started by: salil2012
3 Replies
5. AIX
Dear Friends ,
I am using DB2 database in AIX 5.3 server . In my server some IDLE process are generated after several times which I need to kill it manually each and every time .
The process I query like following :
root@bagpuss $ ps auxw|sort -r +3|head -10
USER PID %CPU %MEM ... (3 Replies)
Discussion started by: shipon_97
3 Replies
6. Shell Programming and Scripting
Hi All,I have a problem with my kill idle script.my script is supposed to kill the user sessions which are idle for more than 2 hours.But is is killing the sessions which are idle for less than 2 hrs also.I dont know the exact time after which the script is killing,but it is less than 2 hours i am... (3 Replies)
Discussion started by: prabhu_kumar
3 Replies
7. Solaris
Hi,
i need to kill the idle dt sessions through script, can anyone tell me how to do?
RJS (2 Replies)
Discussion started by: rajasekg
2 Replies
8. Shell Programming and Scripting
Hello..
I have many sleepy users on my Solaris box and need to kill them if they are idle for more than 45 minutes for example...I know who -u gives and the idle time but unable to make a awk line to get the condition perfect. Please help...:wall: (9 Replies)
Discussion started by: wimaxpole
9 Replies
9. Shell Programming and Scripting
Hi,
I need a script that can automatically kill all processes named "webrepn" and "webrebw" if idle for more than 30 minutes.
Then I will have a Cron Job to run the script every night or 2-3 times a day depends on how this script helps.
Right now, I run "ps -ef | grep webrebn" and "kill -9... (7 Replies)
Discussion started by: MaggieL
7 Replies
10. UNIX for Beginners Questions & Answers
Hi Team ,
I have one process named as cec_analysiseool that is running on unix box machine now i want to kill this process so please advise what will be the ideal command to kill this , what i have tried is :confused:
kill -9 `ps -ef | grep cec_analysiseool | grep -v grep | awk '{print $2}'` (2 Replies)
Discussion started by: unclesamm
2 Replies
NICE(1) General Commands Manual NICE(1)
NAME
nice, nohup - run a command at low priority (sh only)
SYNOPSIS
nice [ -number ] command [ arguments ]
nohup command [ arguments ]
DESCRIPTION
Nice executes command with low scheduling priority. If the number argument is present, the priority is incremented (higher numbers mean
lower priorities) by that amount up to a limit of 20. The default number is 10.
The super-user may run commands with priority higher than normal by using a negative priority, e.g. `--10'.
Nohup executes command immune to hangup and terminate signals from the controlling terminal. The priority is incremented by 5. Nohup
should be invoked from the shell with `&' in order to prevent it from responding to interrupts by or stealing the input from the next per-
son who logs in on the same terminal.
FILES
nohup.out standard output and standard error file under nohup
SEE ALSO
csh(1), setpriority(2), renice(8)
DIAGNOSTICS
Nice returns the exit status of the subject command.
BUGS
Nice and nohup are particular to sh(1). If you use csh(1), then commands executed with ``&'' are automatically immune to hangup signals
while in the background. There is a builtin command nohup which provides immunity from terminate, but it does not redirect output to
nohup.out.
Nice is built into csh(1) with a slightly different syntax than described here. The form ``nice +10'' nices to positive nice, and ``nice
-10'' can be used by the super-user to give a process more of the processor.
4th Berkeley Distribution May 8, 1986 NICE(1)