Congratulations! Mine was intentional, back in college, where all PCs had open telnet in order to facilitate cooperation. We discovered it was easy to seize someone's computer for a while, and then watch them look around for the culprit, which we thought was hilarious. Boy were we annoying.
My first was in college on the lab computers, I was like "can I create a pthreads bomb instead to circumvent the fork bomb protections?"
Luckily the head sysadmin knew me and was in the room at the time, and I sheepishly explained by the time I realized it worked it was too late for me to stop it, he seemed understanding, understood it wasn't malicious, and luckily got that what else is a CS department for than for students to learn about this stuff?
A fork bomb can refer to any process that spawns multiple recursive child processes. You don't need fork to spawn more copies of yourself, that is merely the classic Unix implementation.
And they say you can't learn anything about computers from these bots... I had to learn this lesson from giving a shell account to one of my compatriots. I worked with him on group projects so I trusted him. He installed a fork bomb in his user's cron tab that went off at 3:00 a.m. everyday and I had to wonder why my hand compiled DRI driven screensaver went to a crawl. I did learn the lesson and I did forgive him. But it didn't cost me a couple Grand in API fees.
Wasn't my first, but my first unintentional one was writing multiprocessing code with Python on Windows many years ago. Not sure if this is still true now, but if you didn't wrap your main entrypoint in a if __name__ == "__main__" block, and your code spun up a worker pool, Python would reload your module for every child since Windows doesn't have a fork() for it to use, and they'd all happily rerun the code to create children, and so on.
I don't know about the author, but I recently saw an article where the author of Claude code apparently spins up multiple instances at once (note that it could have just been a marketing ploy to get people to use more tokens)
Just use Git worktrees and a lightweight VM environment (I like macOS native sandbox-exec) and you can spawn as many sessions as you want. I've run upwards of 30 at once on my M2 Pro with no noticeable resource impact.
I tend to have multiple sessions running when doing stuff with CC. But rarely in the same space / domain. I'll have one working on some programming task, another making changes to my NAS and another doing research for some other topic (most recently networking gear upgrade paths).
23 comments
Luckily the head sysadmin knew me and was in the room at the time, and I sheepishly explained by the time I realized it worked it was too late for me to stop it, he seemed understanding, understood it wasn't malicious, and luckily got that what else is a CS department for than for students to learn about this stuff?
That was a great early lesson to never trust code you read online. Even if it is from Microsoft’s own developer portal.
I don't use AI for these. My friends edit/give feedback, so the cycle is slow.
https://www.xda-developers.com/set-up-claude-code-like-boris...
SessionEndhook that summarizes the conversation with a bunch of metadata, but it doesn't always fire 'cause of my habits.So, the
SessionStarthook was meant to catch any conversation where theSessionEndhook wasn't fired.Edit: I do realize a batch job is better. That's what I do now.
I told him it was a risk to let dumbasses like us have a shell on his server. He said we couldn't do anything, that they were unprivileged accounts.
"Watch this", says I, as his machine froze.
I got in so much trouble for that. I hope you can't do that kind of thing any more.