3 ms·
> What if you're ssh'd into a machine, you're in your trusty bash shell, but unfortunately you cannot spawn any new processes because literally all other pids
by zoidb 2y ago
> What if you're ssh'd into a machine, you're in your trusty bash shell, but unfortunately you cannot spawn any new processes because literally all other pids are taken. What do you do?
A long ago for fun I created an interactive website to explore this type of scenario. https://oops.cmdchallenge.com https://oops.cmdchallenge.com
- dolmen 2y ago"echo *" doesn't list ALL files in the directory. "echo .* *" does.
- teddyh 2y agoIt does list all files if you run set -O dotglob
- gigatexal 2y agoi would begin to panic and think wtf why am i in this uber-grey-beard-dev-sys-ops interview??? im just a data engineer
- lilyball 2y agoThis is cool, but once I beat it, it just brought me back to the first step and wouldn't let me see the others. That's frustrating because I wanted to check out the "View Solutions" lists for the other steps to see what other approaches I could have taken.