Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Back in 2000, I was working for a small dotcom startup and I remember we came into work one day to discover that our production servers were all running at a crawl & unable to serve traffic. Turned out that one of the devs had installed seti@home on all our servers (this was before devops was a thing) and it was hogging 90%+ of the cpu. I think he'd installed seti on every machine in the office that he could get access to, even other people's workstations. He was utterly obsessed with the thing.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: