10-12-2001
Help on processes not associated with a TTY
Hi all ^_^
Okay, here's the problem:
There's an IBM RS6000 server running AIX 4.3 with Informix database in my workplace. During peak hours, it has about 350 users doing mostly database operations. It has been set up that those users can only log-in the system at one terminal at a time. Due to many reasons (improper disconnection from the system, disrupted connection, etc), some users' processes are hung in the system, eating up system resources, even though they got disconnected. Those processes are the ones without a TTY when examining the output of the command "ps aux"
Thus, our system operators receive a lot of user requests to kill their processes. A shell script is used to kill all processes without a tty(terminal name) belonging to a specified user. Apparantly,
our operators are sick of getting calls to kill those dead processes.
I want to know if there's a way to prevent this problem from happening at all (or decrease the frequency of this problem)
10 More Discussions You Might Find Interesting
1. AIX
Hi All
can anyone tell me what is the meaning of tty,or give me an example of this? (1 Reply)
Discussion started by: magasem
1 Replies
2. 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
3. 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
4. UNIX for Dummies Questions & Answers
Hi All,
Long time reader, first time poster.
I have a tip session to a v480 serial console running Solaris 9.
Look at this mess I'm getting back...
connected... (16 Replies)
Discussion started by: danny.hudson
16 Replies
5. Linux
It's happened multiple times and I can't figure out why it's happening or how to undo it, but hitting CTRL-S seems to disable the given TTY on 'nixes of various flavors. Killing the pid doesn't bring the tty back, I end up having to use other tty's until I reboot.
Anyone got some information for... (2 Replies)
Discussion started by: thmnetwork
2 Replies
6. 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
7. UNIX for Advanced & Expert Users
I am not sure if I am using the correct terminology but somehow my tty keeps changing on me. The man pages are confusing to me on what exactly the tty is. This is what I see when I run the tty command. Could anyone explain why my tty keeps changing?
~ $ tty
/dev/pts/1
~ $ tty
/dev/pts/0 (6 Replies)
Discussion started by: cokedude
6 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I need your help to understand about different processes(tty1,tty2,tty3...) running as root as shown below .What exactly these processes do?
root@bisu-desktop:~# ps -eaf | grep -e tty -e UID
UID PID PPID C STIME TTY TIME CMD
root 761 1 0 10:30 tty5 ... (4 Replies)
Discussion started by: crazybisu
4 Replies
9. Shell Programming and Scripting
In bash, you can do something like this:
#!/bin/bash
echo -n "What is your name? " > /dev/tty
read thename < /dev/tty
How can I do the same in python?
I have a python script that has the following content:
#!/usr/bin/python2.7
import getpass
import sys
import telnetlib
import... (2 Replies)
Discussion started by: SkySmart
2 Replies
10. SCO
Is there an easy to see which /dev/tty a printer is on on SCO Unix 3.2.4.2? (1 Reply)
Discussion started by: steveo314
1 Replies
KILL(1) General Commands Manual KILL(1)
NAME
kill - terminate a process with extreme prejudice
SYNOPSIS
kill [ -sig ] processid ...
kill -l
DESCRIPTION
Kill sends the TERM (terminate, 15) signal to the specified processes. If a signal name or number preceded by `-' is given as first argu-
ment, that signal is sent instead of terminate (see sigvec(2)). The signal names are listed by `kill -l', and are as given in
/usr/include/signal.h, stripped of the common SIG prefix.
The terminate signal will kill processes that do not catch the signal; `kill -9 ...' is a sure kill, as the KILL (9) signal cannot be
caught. By convention, if process number 0 is specified, all members in the process group (i.e. processes resulting from the current
login) are signaled (but beware: this works only if you use sh(1); not if you use csh(1).) Negative process numbers also have special
meanings; see kill(2) for details.
The killed processes must belong to the current user unless he is the super-user.
The process number of an asynchronous process started with `&' is reported by the shell. Process numbers can also be found by using ps(1).
Kill is a built-in to csh(1); it allows job specifiers of the form ``%...'' as arguments so process id's are not as often used as kill
arguments. See csh(1) for details.
SEE ALSO
csh(1), ps(1), kill(2), sigvec(2)
BUGS
A replacement for ``kill 0'' for csh(1) users should be provided.
4th Berkeley Distribution April 20, 1986 KILL(1)