10-08-2001
rouge processes
Often when i do a ps -ef |grep user there are sh processes however the users are not actually logged in. Does any one know what i could do to automatically kill off these processes.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Is it possible to have a main script (i will call it main.ksh) that executes say, 4 other scripts (sub_prog_1.ksh, sub_prog_2.ksh etc..) from within this main.ksh (simultaneously/in parallel), have them run in the background and communicate back to main.ksh when complete?
My guess is to use... (1 Reply)
Discussion started by: google
1 Replies
2. Shell Programming and Scripting
does anyone know how to lower the sheduling priority of a process. (3 Replies)
Discussion started by: master_6ez
3 Replies
3. UNIX for Dummies Questions & Answers
I'm hoping you guys (the experts) can help me.
We have a sweep directory (/opt/application/sweep) critical to our application process. The application will lay down a file in that directory, then about 15 seconds later a post process will come along and pick that file up and continue processing.... (2 Replies)
Discussion started by: hedrict
2 Replies
4. UNIX for Advanced & Expert Users
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
5. Solaris
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)
Discussion started by: wilsonee
2 Replies
6. UNIX for Dummies Questions & Answers
Hi all,
I needed a little help. It's OS thing.
Suppose I have 2 machine connect over a network, I will call my machines as M1and M2.
If I copy a files from M1 to M2. What tasks are these two machine performing for copy to work.
My assumption is that M1 is performing read action and... (1 Reply)
Discussion started by: vishwesh
1 Replies
7. Shell Programming and Scripting
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
8. UNIX for Dummies Questions & Answers
may i know a command to find processes not attached to a terminal?? (1 Reply)
Discussion started by: riya9
1 Replies
9. Post Here to Contact Site Administrators and Moderators
Hi guys this problem exists on all my machines...
Windows 8.1, Ubuntu, iMac and this MBP.
All use fireFox, latest current version.
If I log in there is NOT a problem.
I usually enter this site as an outsider and I have noticed that there is some rouge code and/or advert that slows the... (5 Replies)
Discussion started by: wisecracker
5 Replies
KILL(1) BSD General Commands Manual KILL(1)
NAME
kill -- terminate or signal a process
SYNOPSIS
kill [-s signal_name] pid ...
kill -l [exit_status]
kill -signal_name pid ...
kill -signal_number pid ...
DESCRIPTION
The kill utility sends a signal to the processes specified by the pid operand(s).
Only the super-user may send signals to other users' processes.
The options are as follows:
-s signal_name
A symbolic signal name specifying the signal to be sent instead of the default TERM.
-l [exit_status]
If no operand is given, list the signal names; otherwise, write the signal name corresponding to exit_status.
-signal_name
A symbolic signal name specifying the signal to be sent instead of the default TERM.
-signal_number
A non-negative decimal integer, specifying the signal to be sent instead of the default TERM.
The following pids have special meanings:
-1 If superuser, broadcast the signal to all processes; otherwise broadcast to all processes belonging to the user.
Some of the more commonly used signals:
1 HUP (hang up)
2 INT (interrupt)
3 QUIT (quit)
6 ABRT (abort)
9 KILL (non-catchable, non-ignorable kill)
14 ALRM (alarm clock)
15 TERM (software termination signal)
Some shells may provide a builtin kill command which is similar or identical to this utility. Consult the builtin(1) manual page.
SEE ALSO
builtin(1), csh(1), killall(1), ps(1), kill(2), sigaction(2)
STANDARDS
The kill function is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
HISTORY
A kill command appeared in Version 6 AT&T UNIX.
BUGS
A replacement for the command ``kill 0'' for csh(1) users should be provided.
BSD
April 28, 1995 BSD