06-29-2004
Depends on how you define "hang".... how about
kill -STOP $pid
10 More Discussions You Might Find Interesting
1. Programming
Hi all,
There is a pearent process with 3 child processes, they work perfect. Pearent process read from file and separate data by blocks and send it to child processes, after that pearent read the result of work and just print it out to standart output. All interprocess communication maded through... (2 Replies)
Discussion started by: prodigal
2 Replies
2. Shell Programming and Scripting
Im making a script that goes out to about 200 servers and grabs log files daily and need to make sure the script gets all the servers it can even if one is out. I am ftp'ing the files over but if i cant connect to the server the process looks like it dies and the script is finished. (4 Replies)
Discussion started by: rcunn87
4 Replies
3. UNIX for Advanced & Expert Users
I've tried this a long time ago and was successful but could not remember how i did it. Tried ctrl+Z and then used bg %
could not figure what i did after to keep it no hangup -
not sure if used nohup -p pid, can u plz help me out if this can be done.
Any help will be appreciated. (12 Replies)
Discussion started by: pharos467
12 Replies
4. Solaris
Hi all,
I use latest bind 9.6.1, brand-new T5140 Sun Server, 10u8 Solaris OS, Mar-2010 OS patch to configure a caching dns server.
But bind always hang up when process/cache is reaching to 500 Mb ( Though 'prstat -a' check )
Can anyone help me a solution for this problem, i will greatly... (0 Replies)
Discussion started by: tien86
0 Replies
5. Shell Programming and Scripting
Hi,
Can anyone help to create a script that will kill the process which is in hang state. (1 Reply)
Discussion started by: A.Santhosh
1 Replies
6. IP Networking
Hi, on our Solaris 10 servers, one day 'netstat -a' command return very slow after TCP output, wait 5 minute on this line -
SCTP:
Local Address Remote Address Swind Send-Q Rwind Recv-Q StrsI/O State
------------------------------- ------------------------------- ------ ------ ------ ------... (6 Replies)
Discussion started by: ora_dba
6 Replies
7. Red Hat
Hello,
Sometime i see that the boot process hangs.
I am using rhel 6.2.
At that time in the console i see
Probing EDD (edd=off to disable)...
SSH service seems to be started but i can't login...
ssh logs (last lines) in verbose mode level 3:
debug2: we did not send a packet,... (3 Replies)
Discussion started by: @dagio
3 Replies
8. BSD
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (0 Replies)
Discussion started by: naveeng
0 Replies
9. UNIX for Advanced & Expert Users
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (1 Reply)
Discussion started by: naveeng
1 Replies
10. UNIX for Advanced & Expert Users
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (6 Replies)
Discussion started by: naveeng
6 Replies
SKILL(1) User Commands SKILL(1)
NAME
skill, snice - send a signal or report process status
SYNOPSIS
skill [signal] [options] expression
snice [new priority] [options] expression
DESCRIPTION
These tools are obsolete and unportable. The command syntax is poorly defined. Consider using the killall, pkill, and pgrep commands
instead.
The default signal for skill is TERM. Use -l or -L to list available signals. Particularly useful signals include HUP, INT, KILL, STOP,
CONT, and 0. Alternate signals may be specified in three ways: -9 -SIGKILL -KILL.
The default priority for snice is +4. Priority numbers range from +20 (slowest) to -20 (fastest). Negative priority numbers are
restricted to administrative users.
OPTIONS
-f, --fast
Fast mode. This option has not been implemented.
-i, --interactive
Interactive use. You will be asked to approve each action.
-l, --list
List all signal names.
-L, --table
List all signal names in a nice table.
-n, --no-action
No action; perform a simulation of events that would occur but do not actually change the system.
-v, --verbose
Verbose; explain what is being done.
-w, --warnings
Enable warnings. This option has not been implemented.
-h, --help
Display help text and exit.
-V, --version
Display version information.
PROCESS SELECTION OPTIONS
Selection criteria can be: terminal, user, pid, command. The options below may be used to ensure correct interpretation.
-t, --tty tty
The next expression is a terminal (tty or pty).
-u, --user user
The next expression is a username.
-p, --pid pid
The next expression is a process ID number.
-c, --command command
The next expression is a command name.
--ns pid
Match the processes that belong to the same namespace as pid.
--nslist ns,...
list which namespaces will be considered for the --ns option. Available namespaces: ipc, mnt, net, pid, user, uts.
SIGNALS
The behavior of signals is explained in signal(7) manual page.
EXAMPLES
snice -c seti -c crack +7
Slow down seti and crack commands.
skill -KILL -t /dev/pts/*
Kill users on PTY devices.
skill -STOP -u viro -u lm -u davem
Stop three users.
SEE ALSO
kill(1), kill(2), killall(1), nice(1), pkill(1), renice(1), signal(7)
STANDARDS
No standards apply.
AUTHOR
Albert Cahalan <albert@users.sf.net> wrote skill and snice in 1999 as a replacement for a non-free version.
REPORTING BUGS
Please send bug reports to <procps@freelists.org>
procps-ng October 2011 SKILL(1)