Also you could take information of every java process with ps: ps -ef grep java grep -v grep.
You can see the state of the grep process in the /proc tree: grep State /proc/28814/status You could use ps command to get extended information about command which launched process: ps -fpYou can actually change the filtering condition on grep to find any kind of process. Mtak 28816 28799 0 12:35 pts/17 00:00:00 grep -color=auto bar This means if it's a java process then the java command will be present in the output and that's what we are searching for using the grep command. jconsole pid and then if you go to the VM Summary tab you'll see the entire VM arguments, classpath, etc Display Name is missing at 15:14 The one I have to kill is Java 6 only. Mtak 28814 28799 0 12:35 pts/17 00:00:00 grep -color=auto bla 1 try ps -ef grep yourDomainName Mani at 15:07 Worst case scenario - you can bring up jconsole and connect to the server pids you have running. The shell does not buffer the output and hold it until one process has completed and then transfers it to another process.įor example: tar -zcvf test.tgz /lib/ | grep bla | grep foo | grep bar
grep matches lines which match a regular expression. muru at 6:01 Add a comment 2 Answers Sorted by: 2 The command ps -ax displays yours as well as other users' processes. When piping commands, all processes are started at the same time and they just sleep (block) until I/O enters/exits them. at 20:32 Please don't add tags to the title.
0 kommentar(er)
