Tag Info

New answers tagged


All the instances of Mate Terminal have the same PID because they are in fact a single process which happens to display multiple windows. Mate Terminal runs in a single process because that's the way the application is designed. When you run the command mate-terminal, it contacts the existing process and sends it an instruction to open a new window. As of ...


I am completely ignorant of mate terminal, but from the sounds of it, the program may be multi-threaded. Threads share the same PID.


Try the control groups (cgroups) facility. Introduced since Linux 2.6.24, it is a very flexible tool to assign CPU shares to processes as well as to place caps on resource (blockio, network, memory) utilization for each process. Here's documentation.


Use the command "renice" to change a process priority


vi-vi-vi is of the devil. You must kill it with fire. Or SIGKILL: kill -KILL %1 The builtin kills are kind enough to send SIGCONT to suspended processes so that you don't have to do it yourself, but that won't help if the process blocks the signal you're sending or if handling the signal causes the processes to become suspended again (if a background ...


vim is installing signal handlers (and probably also setting sigprocmask(2)) to ignore common signals so that any files being edited are not lost due to a stray control+c or random kill signal. A simpler program is readily killed: % cat busyloop.c int main(void) { for (;;) { ; } return 0; } % make busyloop cc busyloop.c -o busyloop % ./busyloop ^Z zsh: ...


Do you have a link for the particular 7-state process model? Generally, blocked processes are put on queues belonging to the events they are waiting for, so the answer would be no. Only the blocked/ready processes would be on a run queue (and even then, depending on the scheduler and number of cores there could be multiple run queues).


Actually, you don't have to grep anything when using ps, run this: ps -o cmd= -C bash

Top 50 recent answers are included