Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Killing idle user processes
Top Forums UNIX for Dummies Questions & Answers Killing idle user processes Post 19588 by mikek147 on Saturday 13th of April 2002 05:42:23 PM
Old 04-13-2002
Uning the kill command with the signal of 9 is a dangerous way of terminating a process. The 9 signal is an absolute and unblockable form of termination. This means that if a process has, for example, multiple files open or has a database open, although the user may be gone, the files can remain open or the database left in an unstable condition.

If you must kill a process, use kill with signal 15 or without a signal. Using kill without a signal, it defaults to signal 15 anyway, which notifies the offending process to shut down. If the process is written correctly, it will close down transactions or any open files and exit cleanly. -mk
 

10 More Discussions You Might Find Interesting

1. Cybersecurity

Killing Idle session

does any one know how to kill an idle session? I want to kill any idle sessions after 30 min... Local or remote.... i want to do this without a script or TCP wrappers...i want to know if there is a file that i can configure..... ThAnks:rolleyes: (4 Replies)
Discussion started by: securhack
4 Replies

2. Solaris

killing all processes for an user

how can I kill all the processes belonging to an user. I need it because I can't see a process initiated by a user and thus unable to kill it. (2 Replies)
Discussion started by: krishan
2 Replies

3. Shell Programming and Scripting

script for killing idle users

I need a script that will look for idle users and kill there proc. (7 Replies)
Discussion started by: jdel80
7 Replies

4. Shell Programming and Scripting

killing cascade processes

Hi everybody!! I've got a problem. I have a loop like this: while true; do some_work sleep 10m done It's possible to kill the main loop process and kill all childs from it? I want to kill main process and kill the sleep also. I tried kill -9 <loop_pid> with no result ... (4 Replies)
Discussion started by: victorin
4 Replies

5. Shell Programming and Scripting

i need a scipt to email users with idle processes!?

hello, i am VERY new to this whole script world. I need to come up with a script that will email a user if they have an idle process past 500 minutes...any suggestions??? Thanks so much. (0 Replies)
Discussion started by: sheppy28
0 Replies

6. Shell Programming and Scripting

Killing idle users TIA

I wrote a script to kill users idle more than 1/2 hour, ignoring those in an exception list. Here is the script as it is now: #! /usr/bin/awk -f BEGIN { system("who -u | sort +5 > /tmp/loginfile"); system("echo User Sessions Killed > /tmp/killedlogins"); ... (2 Replies)
Discussion started by: PapaBear
2 Replies

7. UNIX for Advanced & Expert Users

Monitoring Processes - Killing hung processes

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)
Discussion started by: ukndoit
4 Replies

8. UNIX for Advanced & Expert Users

killing all child processes

Hi, Is there a way I can kill all the child processes of a process, given its process id. Many thanks in advance. J. (1 Reply)
Discussion started by: superuser84
1 Replies

9. Shell Programming and Scripting

Kill idle script is killing unnecessarly

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

10. Shell Programming and Scripting

Finding the age of a unix process, killing old processes, killing zombie processes

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)
Discussion started by: sukerman
0 Replies

LEARN ABOUT OSF1

rusers

rusers(1)						      General Commands Manual							 rusers(1)

NAME

       rusers - Display a list of users who are logged in to a remote machine

SYNOPSIS

       rusers [-ahilu] host...

OPTIONS

       Give  a	report for a machine even if no users are logged in.  Sort alphabetically by host name.  Sort by idle time.  Give a longer listing
       in the style of who(1).	Sort by number of users.

DESCRIPTION

       The rusers command displays information about users and processes running on remote machines.   The  listing  is  in  the  order  in  which
       responses are received, but this order can be changed by specifying one of the options listed in the OPTIONS section.

       By default the rusers command prints the names of the users logged in.	When the -l option is given, additional information is printed for
       each user, as follows:

       userid hostname:terminal login date login time idle time login host

       If hostname and login host are the  same  value, the login host field is not displayed.	Likewise, if hostname is not idle, the	idle  time
       is not displayed. A remote host only responds if it is running the rusersd daemon, which may be started from the inetd daemon or the listen
       function.

SEE ALSO

       Commands: who(1), inetd(8)

       Functions: listen(2)

																	 rusers(1)
All times are GMT -4. The time now is 11:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy