There’s no such specifier. I think what you’re doing (casting the pid_t to long and printing it with “%ld”) is fine; you could use an even wider int type, but there’s no implementation where pid_t is bigger than long and probably never will be.
As every application has its own process id, one can get it by int pid = android.os.Process.myPid();
After a lot of searching, I was able to fix the “PID file cannot be found” issue on my machine. I’m on OS X 10.9.3 and installed mysql via Homebrew. First, I found my PID file here: /usr/local/var/mysql/{username}.pid Next, I located my my.cnf file here: /usr/local/Cellar/mysql/5.6.19/my.cnf Finally, I added this line to the bottom of … Read more
You can get the pid of processes by name using pidof through subprocess.check_output: from subprocess import check_output def get_pid(name): return check_output([“pidof”,name]) In [5]: get_pid(“java”) Out[5]: ‘23366\n’ check_output([“pidof”,name]) will run the command as “pidof process_name”, If the return code was non-zero it raises a CalledProcessError. To handle multiple entries and cast to ints: from subprocess import … Read more
If you want to kill -9 based on a string (you might want to try kill first) you can do something like this: ps axf | grep <process name> | grep -v grep | awk ‘{print “kill -9 ” $1}’ This will show you what you’re about to kill (very, very important) and just pipe … Read more
Another option: use a redirect to subshell. This changes the order in which background processes are started, so $! gives PID of the tail process. tail -f $1 > >(nc -l -p 9977) & wait $!
With all due respect to the users of pgrep, pkill, ps | awk, etc, there is a much better way. Consider that if you rely on ps -aux | grep … to find a process you run the risk of a collision. You may have a use case where that is unlikely, but as a … Read more
The answer above was mostly correct, just needed some tweaking for the different parameters in Mac OSX. ps -A | grep [f]irefox | awk ‘{print $1}’
I think it is easier to use pgrep $ pgrep bluetoothd 441 Otherwise, you can use awk: ps -ef | awk ‘$8==”name_of_process” {print $2}’ For example, if ps -efhas a line like: root 441 1 0 10:02 ? 00:00:00 /usr/sbin/bluetoothd Then ps -ef | awk ‘$8==”/usr/sbin/bluetoothd” {print $2}’ returns 441. In ksh pgrep is not … Read more
It is complicated: pid is process identifier; tid is thread identifier. But as it happens, the kernel doesn’t make a real distinction between them: threads are just like processes but they share some things (memory, fds…) with other instances of the same group. So, a tid is actually the identifier of the schedulable object in … Read more