Could upstart track an arbitrary number of forks? instead of limiting to 1 (expect fork) or 2 (expect daemon) could expect N be supported?
Also here is a bash script to exhaust the pid space if your system does not have ruby.
pass the pid upstart is waiting for as an argument like this exhaustPIDspace.sh 11920
#!/bin/bash
usleep 1 & firstPID=$! #first lets exhaust the space while [ $! -ge $firstPID ] do usleep 1 & done
while [ $! -le $1 ] do usleep 1 & done
Could upstart track an arbitrary number of forks? instead of limiting to 1 (expect fork) or 2 (expect daemon) could expect N be supported?
Also here is a bash script to exhaust the pid space if your system does not have ruby.
pass the pid upstart is waiting for as an argument like this exhaustPIDspace.sh 11920
#!/bin/bash
usleep 1 &
firstPID=$!
#first lets exhaust the space
while [ $! -ge $firstPID ]
do
usleep 1 &
done
while [ $! -le $1 ]
do
usleep 1 &
done