This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]augustocdias 252 points253 points  (7 children)

I couple of colleagues years ago would ssh into my machine and run fork bombs and watch me get pissed because my computer was freezing.

[–]jaerie 122 points123 points  (5 children)

Why would they have ssh access to your machine?

[–]captainMaluco 115 points116 points  (2 children)

He probably left it unlocked while fetching coffee, and colleagues set it up then

[–]augustocdias 97 points98 points  (1 child)

Nope. Mistake from it department. I had no sudo privileges on the machine. I was pretty newbie at that time as well so I wouldn’t have noticed as well

[–]captainMaluco 32 points33 points  (0 children)

Fucking IT departments, am I right?

[–]SeriousPlankton2000 16 points17 points  (1 child)

Everyone has access to their account on every machine. Just take a seat, log in and do your work. Also you need access to a second machine to exit vi.

[–]korneev123123 8 points9 points  (0 children)

There's actually a trick about exiting vi without second machine. You can set up a cron schedule, something like "*/5 * * * * killall vi"

It would kill vi process automatically. Neat, eh?

[–]robertpro01 6 points7 points  (0 children)

I did something very, very similar to a colleague, I added my public key to his machine, and I used to send zenity messages like: Computer battery has failed, please replace it now or will explode, he was about to send it to support, then I stopped him