查看进程和进程强行干掉命令

来源：互联网发布：android 源码精简编辑：程序博客网时间：2024/05/16 12:35

1、名称查询（以flume为例）：

[laps@hn10 logs]$ ps -jafx|grep flume

查询结果为（两种都可以）：

[laps@hn10 logs]$ ps -jafx|grep flume
Warning: bad syntax, perhaps a bogus '-'? See /usr/share/doc/procps-3.2.7/FAQ
24126 1222 1221 24126 pts/2     1221 S+     500   0:00 |           \_ grep flume
    1 22623 22622 22399 ?           -1 Sl     500   3:45 /home/laps/flume/jdk/bin/java -Xmx1000m -cp /home/laps/flume/flume/conf:/home/laps/flume/flume/lib/*:/lib/* -Djava.library.path= org.apache.flume.node.Application -n aK -f conf/flume-conf.properties
    1 29543 29542 24126 pts/2     1221 Sl     500   0:13 /home/laps/flume/jdk/bin/java -Xmx1000m -cp /home/laps/flume/flume/conf:/home/laps/flume/flume/lib/*:/lib/* -Djava.library.path= org.apache.flume.node.Application -n aK -f conf/flume-conf.properties
[laps@hn10 logs]$ ps -jafx|grep -E "PID|flume"
Warning: bad syntax, perhaps a bogus '-'? See /usr/share/doc/procps-3.2.7/FAQ
PPID   PID PGID   SID TTY      TPGID STAT   UID   TIME COMMAND
24126 1234 1233 24126 pts/2     1233 S+     500   0:00 |           \_ grep -E PID|flume
    1 22623 22622 22399 ?           -1 Sl     500   3:45 /home/laps/flume/jdk/bin/java -Xmx1000m -cp /home/laps/flume/flume/conf:/home/laps/flume/flume/lib/*:/lib/* -Djava.library.path= org.apache.flume.node.Application -n aK -f conf/flume-conf.properties
    1 29543 29542 24126 pts/2     1233 Sl     500   0:13 /home/laps/flume/jdk/bin/java -Xmx1000m -cp /home/laps/flume/flume/conf:/home/laps/flume/flume/lib/*:/lib/* -Djava.library.path= org.apache.flume.node.Application -n aK -f conf/flume-conf.properties

2、杀死进程：

[laps@hn10 logs]$ kill -9 22623
[laps@hn10 logs]$ kill -9 29543

备注：

kill 命令参数：

linux signals

Signal NameNumberDescriptionSIGHUP1Hangup (POSIX)SIGINT2Terminal interrupt (ANSI)SIGQUIT3Terminal quit (POSIX)SIGILL4Illegal instruction (ANSI)SIGTRAP5Trace trap (POSIX)SIGIOT6IOT Trap (4.2 BSD)SIGBUS7BUS error (4.2 BSD)SIGFPE8Floating point exception (ANSI)SIGKILL9Kill(can't be caught or ignored) (POSIX)SIGUSR110User defined signal 1 (POSIX)SIGSEGV11Invalid memory segment access (ANSI)SIGUSR212User defined signal 2 (POSIX)SIGPIPE13Write on a pipe with no reader, Broken pipe (POSIX)SIGALRM14Alarm clock (POSIX)SIGTERM15Termination (ANSI)SIGSTKFLT16Stack faultSIGCHLD17Child process has stopped or exited, changed (POSIX)SIGCONT18Continue executing, if stopped (POSIX)SIGSTOP19Stop executing(can't be caught or ignored) (POSIX)SIGTSTP20Terminal stop signal (POSIX)SIGTTIN21Background process trying to read, from TTY (POSIX)SIGTTOU22Background process trying to write, to TTY (POSIX)SIGURG23Urgent condition on socket (4.2 BSD)SIGXCPU24CPU limit exceeded (4.2 BSD)SIGXFSZ25File size limit exceeded (4.2 BSD)SIGVTALRM26Virtual alarm clock (4.2 BSD)SIGPROF27Profiling alarm clock (4.2 BSD)SIGWINCH28Window size change (4.3 BSD, Sun)SIGIO29I/O now possible (4.2 BSD)SIGPWR30Power failure restart (System V)

0 0