Use flock(1) to make an exclusive scoped lock a on file descriptor. This way you can even synchronize different parts of the script. #!/bin/bash ( # Wait for lock on /var/lock/.myscript.exclusivelock (fd 200) for 10 seconds flock -x -w 10 200 || exit 1 # Do stuff ) 200>/var/lock/.myscript.exclusivelock This ensures that code between ( … Read more
<p:commandXxx process> <p:ajax process> <f:ajax execute> The process attribute is server side and can only affect UIComponents implementing EditableValueHolder (input fields) or ActionSource (command fields). The process attribute tells JSF, using a space-separated list of client IDs, which components exactly must be processed through the entire JSF lifecycle upon (partial) form submit. JSF will then … Read more
I think you just want this: var process = Process.Start(…); process.WaitForExit(); See the MSDN page for the method. It also has an overload where you can specify the timeout, so you’re not potentially waiting forever.
The best way is: if ps -p $PID > /dev/null then echo “$PID is running” # Do something knowing the pid exists, i.e. the process with $PID is running fi The problem with kill -0 $PID is that the exit code will be non-zero even if the process is running and you don’t have permission … Read more
Child can ask kernel to deliver SIGHUP (or other signal) when parent dies by specifying option PR_SET_PDEATHSIG in prctl() syscall like this: prctl(PR_SET_PDEATHSIG, SIGHUP); See man 2 prctl for details. Edit: This is Linux-only
vfork() is an obsolete optimization. Before good memory management, fork() made a full copy of the parent’s memory, so it was pretty expensive. since in many cases a fork() was followed by exec(), which discards the current memory map and creates a new one, it was a needless expense. Nowadays, fork() doesn’t copy the memory; … Read more
Note: The command in the question uses Start-Process, which prevents direct capturing of the target program’s output. Generally, do not use Start-Process to execute console applications synchronously – just invoke them directly, as in any shell. Doing so keeps the application connected to the calling console’s standard streams, allowing its output to be captured by … Read more
Linux uses a 1-1 threading model, with (to the kernel) no distinction between processes and threads — everything is simply a runnable task. * On Linux, the system call clone clones a task, with a configurable level of sharing, among which are: CLONE_FILES: share the same file descriptor table (instead of creating a copy) CLONE_PARENT: … Read more
Check out the “nohup” program.
You’re pretty much correct, but threads share all segments except the stack. Threads have independent call stacks, however the memory in other thread stacks is still accessible and in theory you could hold a pointer to memory in some other thread’s local stack frame (though you probably should find a better place to put that … Read more