this post was submitted on 14 Dec 2023
198 points (98.1% liked)

Asklemmy

43905 readers
1039 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy ๐Ÿ”

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] beardedmoose@lemmy.world 31 points 11 months ago (2 children)

This is actually my own Oh Shit story.

Early days of being a sysadmin and making changes on a major Linux server that we have in production. Running routine commands and changing permissions on a few directories and I make a typo. "sudo chmod 777 /etc/" instead of typing the rest of the directory tree I accidentally hit return.

It only ran for a fraction of a second before I hit CTRL + C to stop it but by then the damage had been done. I spent hours mirroring and fixing permissions by hand using a duplicate physical server. As a precaution we moved all production services off this machine and it was a good thing too as when we rebooted the server a few weeks later, it never booted again.

For those that don't know, chmod is used to set access permissions on files and folders, the 777 stands for "Read + Write + Execute" for the owner, group, and everyone else. The /etc directory contains many of the basic system configuration files for the entire operating system and many things have very strict permissions for security reasons. Without certain permissions in place those systems will refuse to load files or boot if not properly set.

[โ€“] Dio9sys@lemmy.blahaj.zone 12 points 11 months ago

That is literally a nightmare scenario for me, holy shit

[โ€“] Djtecha@lemm.ee 3 points 11 months ago (2 children)

If you didn't use the recursion flag this wouldn't be to bad

[โ€“] beardedmoose@lemmy.world 6 points 11 months ago

in hindsight I should have just changed into the directory directly first then used chmod without needing the full path. Or run the flag that asks you to confirm each transaction or dry run. I'm a much smarter idiot nowadays.

[โ€“] Hadriscus@lemm.ee 1 points 11 months ago (1 children)

would that mean it doesn't affect anything other than top level files ?

[โ€“] Djtecha@lemm.ee 1 points 11 months ago

Yea without the R flag it only does the file (and since folders are files in Unix...)