Printed process ids < A.B.C > are composed of 6: A, the node number (0 is the local node, an arbitrary number for a remote node) B, the first 15 bits of the process number (an index into the process table) 7 C, bits 16-18 of the process number (the same process number as B) … Read more
It’s 32768 by default, you can read the value on your system in /proc/sys/kernel/pid_max. And you can set the value higher on 64-bit systems (up to 222 = 4,194,304) with: echo 4194304 > /proc/sys/kernel/pid_max Read more here: http://www.cs.wisc.edu/condor/condorg/linux_scalability.html (via archive.org)
I wouldn’t put a pidfile under an application installation directory such as /opt/my_app/whatever. This directory could be mounted read-only, could be shared between machines, could be watched by a daemon that treats any change there as a possible break-in attempt… The normal location for pidfiles is /var/run. Most unices will clean this directory on boot; … Read more
As new processes fork in, PIDs will increase to a system-dependent limit and then wrap around. The kernel will not reuse a PID before this wrap-around happens. The limit (maximum number of pids) is /proc/sys/kernel/pid_max. The manual says: /proc/sys/kernel/pid_max (since Linux 2.5.34) This file specifies the value at which PIDs wrap around (i.e., the value … Read more
Since Java 9 class Process has new method long pid(), so it is as simple as ProcessBuilder pb = new ProcessBuilder(“cmd”, “/c”, “path”); try { Process p = pb.start(); long pid = p.pid(); } catch (IOException ex) { // … }
I had the same problem today on Mac Sierra. In Mac Sierra you can find postmaster.pid inside /Users/<user_name>/Library/Application Support/Postgres/var-9.6. Delete postmaster.pid and problem will be fixed.
Short version which you can pass to kill command: lsof -i:80 -t
Resetting the content and settings in the simulator worked for me. This is available in the “iOS Simulator” menu.
The four threads will have the same PID but only when viewed from above. What you (as a user) calls a PID is not what the kernel (looking from below) calls a PID. In the kernel, each thread has its own ID, called a PID, although it would possibly make more sense to call this … Read more
Advisory locking has been used for ages and it can be used in bash scripts. I prefer simple flock (from util-linux[-ng]) over lockfile (from procmail). And always remember about a trap on exit (sigspec == EXIT or 0, trapping specific signals is superfluous) in those scripts. In 2009 I released my lockable script boilerplate (originally … Read more