08-16-2006
Urgent problem with SIGCONT and Fedora 4 :(
Hello,
I stop a process with kill -s SIGSTOP, but when I try to restart it with kill -s SIGCONT it do nothing.
I use Fedora Core 4.
Thank you a lot
10 More Discussions You Might Find Interesting
1. Linux
in fedora core 2 with enforcing mode in selinux , why even as a root OS doesnt give permission to create any directory or file in /home ? (1 Reply)
Discussion started by: the.last.soul
1 Replies
2. Linux
Hi all,
I'm experiencing a problem with Fedora Core 4, by which I don't know how to export a directory exclusively in NFSv3.
I have two raid arrays "/dev/md0" and "/dev/md1" both to be visible to SGI machines via NFSv3...
My situation is that Fedora runs NFSv4 and that causes problems with the... (0 Replies)
Discussion started by: spaceace13666
0 Replies
3. Gentoo
HI,
I installed fedora core 6 on my inspiron 1501. After I boot it gives me the following error,
PCI: BIOS BUG #81(00000000) found. (1 Reply)
Discussion started by: linuxuser
1 Replies
4. Linux
hi all
i am currently using fedora core 3 . i downloaded the iso image of fedora core 6 but after installing the fedora core 6 . while starting linux it gives a error saying init is been killed .
wht is happened?
thank u (3 Replies)
Discussion started by: nageshrk
3 Replies
5. Programming
hi,
accept() seems to be still blocking after socket is being closed on our Fedora 8 build. not sure if this is a common problem because i have never experienced this on any other platforms, however i have seen someone else having this issue on Redhat 7 and 9. so is there a socket option fedora... (10 Replies)
Discussion started by: Akimaki
10 Replies
6. Linux
Problem about Fedora directory permission,can anyone help me?
In fedora,I have two ordinary user named user1&user2 in different
groups,when I logined user1 and created a dir named test/ in '/home/
user1/',and do 'chmod 750 test',so when 'ls -l',it appears 'drwxr-
x---' for 'test',but when I... (3 Replies)
Discussion started by: zhouq3132
3 Replies
7. Red Hat
Hi guys
i installed fedora 9 in my system.
i installed perl-devel rpm and perl-5.10.0 rpm.
But perlcc not in /usr/bin/ directory.But perl,perldoc binaris installed.
i am new one for linux. (3 Replies)
Discussion started by: viveksnv
3 Replies
8. SuSE
I appeal to all those of you that have experience with Fedora 9 for help. I am trying to install a suite of software which tries to make changes to the /etc/dhcpd.conf file. After the changes have been made the dhcpd service will not start and the original conf file is restored. However dhcpd... (1 Reply)
Discussion started by: johnf
1 Replies
9. Linux
Hi there, I'm having a bit of a strange problem which I would appreciate some help with.
The Problem:
I have two external hard drives, but I'm borrowing one off my parents to copy data too (one of mine, which is identical to theirs - WD MyBook 300g - is on its way out).
Fedora 9 recognizes... (3 Replies)
Discussion started by: lasthidingplace
3 Replies
10. Linux
Hello,
Can anyone please explain HOW Crontab i.e. job scheduling daemon works in Fedora and CentOS or any Linux platform(Ubuntu)....
What are the points that i have to take care of if have to include a script to be run at a specific scheduled time.
URGENT reply requested. Please help (1 Reply)
Discussion started by: Vabiosis
1 Replies
KILL(1) Linux User's Manual KILL(1)
NAME
kill - send a signal to a process
SYNOPSIS
kill [ -signal | -s signal ] pid ...
kill [ -L | -V, --version ]
kill -l [ signal ]
DESCRIPTION
The default signal for kill 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. Negative PID values may be used to choose whole process
groups; see the PGID column in ps command output. A PID of -1 is special; it indicates all processes except the kill process itself and
init.
SIGNALS
The signals listed below may be available for use with kill. When known constant, numbers and default behavior are shown.
Name Num Action Description
0 0 n/a exit code indicates if a signal may be sent
ALRM 14 exit
HUP 1 exit
INT 2 exit
KILL 9 exit cannot be blocked
PIPE 13 exit
POLL exit
PROF exit
TERM 15 exit
USR1 exit
USR2 exit
VTALRM exit
STKFLT exit might not be implemented
PWR ignore might exit on some systems
WINCH ignore
CHLD ignore
URG ignore
TSTP stop might interact with the shell
TTIN stop might interact with the shell
TTOU stop might interact with the shell
STOP stop cannot be blocked
CONT restart continue if stopped, otherwise ignore
ABRT 6 core
FPE 8 core
ILL 4 core
QUIT 3 core
SEGV 11 core
TRAP 5 core
SYS core might not be implemented
EMT core might not be implemented
BUS core core dump might fail
XCPU core core dump might fail
XFSZ core core dump might fail
NOTES
Your shell (command line interpreter) may have a built-in kill command. You may need to run the command described here as /bin/kill to
solve the conflict.
EXAMPLES
kill -9 -1
Kill all processes you can kill.
kill -l 11
Translate number 11 into a signal name.
kill -L
List the available signal choices in a nice table.
kill 123 543 2341 3453
Send the default signal, SIGTERM, to all those processes.
SEE ALSO
pkill(1), skill(1), kill(2), renice(1), nice(1), signal(7), killall(1).
STANDARDS
This command meets appropriate standards. The -L flag is Linux-specific.
AUTHOR
Albert Cahalan <albert@users.sf.net> wrote kill in 1999 to replace a bsdutils one that was not standards compliant. The util-linux one
might also work correctly.
Please send bug reports to <procps-feedback@lists.sf.net>
Linux November 21, 1999 KILL(1)