tillo
Verified User
The .custombuild file is meant to keep CustomBuild from running if there is an instance running, but:
- if I send a SIGTERM to a running CustomBuild, it doesn't remove the lock file
- if I run a concurrent CustomBuild it doesn't run any function but it removes the lock file when exiting, which is just plain wrong
- if I run a concurrent CustomBuild to compile PHP (maybe others too, didn't check) it doesn't compile but it will restart Apache anyway
If the developer didn't know about it, bash can definitely trap signals: http://tldp.org/LDP/Bash-Beginners-Guide/html/sect_12_02.html
- if I send a SIGTERM to a running CustomBuild, it doesn't remove the lock file
- if I run a concurrent CustomBuild it doesn't run any function but it removes the lock file when exiting, which is just plain wrong
- if I run a concurrent CustomBuild to compile PHP (maybe others too, didn't check) it doesn't compile but it will restart Apache anyway
If the developer didn't know about it, bash can definitely trap signals: http://tldp.org/LDP/Bash-Beginners-Guide/html/sect_12_02.html