10-02-2015
Hi Della,
Filter out the PID "1", it's the "init process" you shouldn't be able to "kill" it. But on the off chance that you somehow manage it, I'll point out that you are unlikely to like the results.
Regards
Dave
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hi, i kill a process which is topas. then i do a fg of the process itself and got this Signal 15 received.finally, the display went as belows....
root@myhost:/]ksh: ^L^L^Lps: not found.
root@myhost:/] PID TTY TIME CMD
... (4 Replies)
Discussion started by: yls177
4 Replies
2. Shell Programming and Scripting
Hi there, i wonder if anyone can help
is there any way that i can write a script that will kill all current ftp processes, for example if ps -ef | grep ftp produces 3 active proceses, then I would like to somehow extract the PID for each one and pass that to kill -9
has anybody done this... (2 Replies)
Discussion started by: hcclnoodles
2 Replies
3. Shell Programming and Scripting
Hi All,
In my project i have two process runs in the back end.
Once i start my project, and execute the command ps, i get below output:
PID TTY TIME CMD
9086 pts/1 0:00 ksh
9241 pts/1 0:02 java
9240 pts/1 0:00 shell_script_bg
java with 9241 PID is the main... (4 Replies)
Discussion started by: rkrgarlapati
4 Replies
4. UNIX for Advanced & Expert Users
Hellow Experts
i have one problem.
i run one script in backgroun.
and i want to kill that script with only script name.....
so what's the solution..
for your info
my script name is "testscript" n it contains "sleep 100"
thanks.... (16 Replies)
Discussion started by: luckypower
16 Replies
5. Shell Programming and Scripting
Hi,
On my Linux machine, using Bash, I sometimes run into a situation where doing the following does not seem to work at all.
kermit@fastbox ~ $ ps -A | grep firefox-bin
5375 ? 00:06:57 firefox-bin <defunct>
5624 ? 00:00:00 firefox-bin
kermit@fastbox ~ $ kill 5624... (7 Replies)
Discussion started by: kermit
7 Replies
6. AIX
Hi all,
I am generating the coredump of my JBoss, and by default it puts it in to a particular directory. i.e. JBOSS_HOME/. I would like this output file to be created, lets say in /tmp/dump/.
I tried the following:
kill -3 9404940>/tmp/dump/out.txt
But it created... (3 Replies)
Discussion started by: haroon_a
3 Replies
7. UNIX for Dummies Questions & Answers
Hello,
I have problem with killing red5 process running on linux server. As this process is continuously changing its PID so it can't be killed with "kill -9 PID" command.
First I used following command to list RED5 process
ps aux | grep red5
which showed me
root 5832 0.0 0.0 4820 756pts/0... (1 Reply)
Discussion started by: ninadgac
1 Replies
8. Shell Programming and Scripting
Hello,
I have problem with killing red5 process running on linux server. As this process is continuously changing its PID so it can't be killed with "kill -9 PID" command.
First I used following command to list RED5 process
ps aux | grep red5
which showed me
root 5832 0.0 0.0 4820 756pts/0... (4 Replies)
Discussion started by: ninadgac
4 Replies
9. Shell Programming and Scripting
Hi,
I wrote a script to kill a process id.
I am able to kill the PID only if I enter the root password in the middle of the execution because I did not run as root i.e after i run the script from the terminal, instead of killing directly, it is killing only after entering the pass when it... (12 Replies)
Discussion started by: rajkumarme_1
12 Replies
10. Shell Programming and Scripting
Hello Friends,
I've been trying to write a one line which checks java processes and filter them for a user (testuser) and then check process arguments with PARGS command and then check if there is certain patterns exists in pargs output then kill the process.
I have tried the following so... (2 Replies)
Discussion started by: EAGL€
2 Replies
LEARN ABOUT FREEBSD
pdkill
PDFORK(2) BSD System Calls Manual PDFORK(2)
NAME
pdfork, pdgetpid, pdkill, pdwait4 -- System calls to manage process descriptors
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <sys/procdesc.h>
pid_t
pdfork(int *fdp, int flags);
int
pdgetpid(int fd, pid_t *pidp);
int
pdkill(int fd, int signum);
int
pdwait4(int fd, int *status, int options, struct rusage *rusage);
DESCRIPTION
Process descriptors are special file descriptors that represent processes, and are created using pdfork(), a variant of fork(2), which, if
successful, returns a process descriptor in the integer pointed to by fdp. Processes created via pdfork() will not cause SIGCHLD on termina-
tion. pdfork() can accept the flags:
PD_DAEMON Instead of the default terminate-on-close behaviour, allow the process to live until it is explicitly killed with kill(2).
This option is not permitted in capsicum(4) capability mode (see cap_enter(2)).
pdgetpid() queries the process ID (PID) in the process descriptor fd.
pdkill() is functionally identical to kill(2), except that it accepts a process descriptor, fd, rather than a PID.
pdwait4() behaves identically to wait4(2), but operates with respect to a process descriptor argument rather than a PID.
The following system calls also have effects specific to process descriptors:
fstat(2) queries status of a process descriptor; currently only the st_mode, st_birthtime, st_atime, st_ctime and st_mtime fields are
defined. If the owner read, write, and execute bits are set then the process represented by the process descriptor is still alive.
poll(2) and select(2) allow waiting for process state transitions; currently only POLLHUP is defined, and will be raised when the process
dies. Process state transitions can also be monitored using kqueue(2) filter EVFILT_PROCDESC; currently only NOTE_EXIT is implemented.
close(2) will close the process descriptor unless PD_DAEMON is set; if the process is still alive and this is the last reference to the
process descriptor, the process will be terminated with the signal SIGKILL.
RETURN VALUES
pdfork() returns a PID, 0 or -1, as fork(2) does.
pdgetpid() and pdkill() return 0 on success and -1 on failure.
pdwait4() returns a PID on success and -1 on failure.
ERRORS
These functions may return the same error numbers as their PID-based equivalents (e.g. pdfork() may return the same error numbers as
fork(2)), with the following additions:
[EINVAL] The signal number given to pdkill() is invalid.
[ENOTCAPABLE] The process descriptor being operated on has insufficient rights (e.g. CAP_PDKILL for pdkill()).
SEE ALSO
close(2), fork(2), fstat(2), kill(2), poll(2), wait4(2), capsicum(4), procdesc(4)
HISTORY
The pdfork(), pdgetpid(), pdkill() and pdwait4() system calls first appeared in FreeBSD 9.0.
Support for process descriptors mode was developed as part of the TrustedBSD Project.
AUTHORS
These functions and the capability facility were created by Robert N. M. Watson <rwatson@FreeBSD.org> and Jonathan Anderson
<jonathan@FreeBSD.org> at the University of Cambridge Computer Laboratory with support from a grant from Google, Inc.
BUGS
pdwait4() has not yet been implemented.
BSD
April 7, 2014 BSD