3 ms·
Upstart leaves you with “exhausting the PID namespace” or rebooting the machine
I seriously regret having switched from sysvinit (!) now.
You have no idea how happy I am right now that I have a machine that managed to get itself into the state where the only real option is a reboot. I feel like thrown back to glorious Windows 98 days.
Especially the amount of debugging information you get out of this service is so wonderful, it was a pleasure to debug.
- the_mitsuhiko 14y agoYou have no idea how happy I am right now that I have a machine that managed to get itself into the state where the only real option is a reboot. I feel like thrown back to glorious Windows 98 days. Especially the amount of debugging information you get out of this service is so wonderful, it was a pleasure to debug.
- lunixbochs 14y agoIf you did want to try exhausting the PID space, I wrote a bash script to do just that (it runs a program with a desired PID): https://github.com/lunixbochs/meta/blob/master/utils/pidrun/pidrun https://github.com/lunixbochs/meta/blob/master/utils/pidrun/... You can use it like this: ./pidrun 23000 cat It might take a few minutes if it needs to wrap around the PID space. When it's done, you'll have a cat process occupying PID 23000, which upstart might be willing to sacrifice.