3 ms·
That engineer should have read the documentation. Failing that a `du -a / | sort -n -r` would immediately show the conclusion you jumped to was wrong. Randomly
by deadbunny 10y ago
That engineer should have read the documentation. Failing that a `du -a / | sort -n -r` would immediately show the conclusion you jumped to was wrong. Randomly bouncing services on a production machine is a cowboy move.
No documentation, no checklists? That's the source of your problem, not a trash command which moves files rather than deleting them.
- jjirsa 10y agoChanging the meaning of a decades old command is the problem - du / can take hours to run on some systems, and randomly bouncing shit in prod is the type of cowboy shit that happens in a panic (see gitlab live doc). Docs and checklists are fine, but at 2am when the jr is on call, you're asking for problems by making rm == mv