Merge pull request #9474 from geekpi/master

translated

sources/talk/20180702 My first sysadmin mistake.md

@@ -1,44 +0,0 @@
-translating---geekpi
-
-My first sysadmin mistake
-======
-
-![](https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/BUSINESS_mistakes.png?itok=dN0OoIl5)
-
-If you work in IT, you know that things never go completely as you think they will. At some point, you'll hit an error or something will go wrong, and you'll end up having to fix things. That's the job of a systems administrator.
-
-As humans, we all make mistakes. Sometimes, we are the error in the process, or we are what went wrong. As a result, we end up having to fix our own mistakes. That happens. We all make mistakes, typos, or errors.
-
-As a young systems administrator, I learned this lesson the hard way. I made a huge blunder. But thanks to some coaching from my supervisor, I learned not to dwell on my errors, but to create a "mistake strategy" to set things right. Learn from your mistakes. Get over it, and move on.
-
-My first job was a Unix systems administrator for a small company. Really, I was a junior sysadmin, but I worked alone most of the time. We were a small IT team, just the three of us. I was the only sysadmin for 20 or 30 Unix workstations and servers. The other two supported the Windows servers and desktops.
-
-Any systems administrators reading this probably won't be surprised to know that, as an unseasoned, junior sysadmin, I eventually ran the `rm` command in the wrong directory. As root. I thought I was deleting some stale cache files for one of our programs. Instead, I wiped out all files in the `/etc` directory by mistake. Ouch.
-
-My clue that I'd done something wrong was an error message that `rm` couldn't delete certain subdirectories. But the cache directory should contain only files! I immediately stopped the `rm` command and looked at what I'd done. And then I panicked. All at once, a million thoughts ran through my head. Did I just destroy an important server? What was going to happen to the system? Would I get fired?
-
-Fortunately, I'd run `rm *` and not `rm -rf *` so I'd deleted only files. The subdirectories were still there. But that didn't make me feel any better.
-
-Immediately, I went to my supervisor and told her what I'd done. She saw that I felt really dumb about my mistake, but I owned it. Despite the urgency, she took a few minutes to do some coaching with me. "You're not the first person to do this," she said. "What would someone else do in your situation?" That helped me calm down and focus. I started to think less about the stupid thing I had just done, and more about what I was going to do next.
-
-I put together a simple strategy: Don't reboot the server. Use an identical system as a template, and re-create the `/etc` directory.
-
-Once I had my plan of action, the rest was easy. It was just a matter of running the right commands to copy the `/etc` files from another server and edit the configuration so it matched the system. Thanks to my practice of documenting everything, I used my existing documentation to make any final adjustments. I avoided having to completely restore the server, which would have meant a huge disruption.
-
-To be sure, I learned from that mistake. For the rest of my years as a systems administrator, I always confirmed what directory I was in before running any command.
-
-I also learned the value of building a "mistake strategy." When things go wrong, it's natural to panic and think about all the bad things that might happen next. That's human nature. But creating a "mistake strategy" helps me stop worrying about what just went wrong and focus on making things better. I may still think about it, but knowing my next steps allows me to "get over it."
-
-
---------------------------------------------------------------------------------
-
-via: https://opensource.com/article/18/7/my-first-sysadmin-mistake
-
-作者：[Jim Hall][a]
-选题：[lujun9972](https://github.com/lujun9972)
-译者：[译者ID](https://github.com/译者ID)
-校对：[校对者ID](https://github.com/校对者ID)
-
-本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
-
-[a]:https://opensource.com/users/jim-hall

translated/talk/20180702 My first sysadmin mistake.md

@@ -0,0 +1,41 @@
+我的第一个系统管理员错误
+======
+
+![](https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/BUSINESS_mistakes.png?itok=dN0OoIl5)
+
+如果你在 IT 领域工作，你知道事情永远不会像你想象的那样完好。在某些时候，你会遇到错误或出现问题，你最终必须解决问题。这是系统管理员的工作。
+
+作为人类，我们都会犯错误。有时，我们是过程中的错误，或者我们出了什么问题。结果，我们最终必须解决自己的错误。它们会发生。我们都犯错误，错别字或故障。
+
+作为一名年轻的系统管理员，我艰难地学到了这一课。我犯了一个大错。但是多亏了上级的指导，我学会了不去纠缠于我的错误，而是制定一个“错误策略”来设置正确的事情。从错误中吸取教训。克服它，继续前进。
+
+我的第一份工作是一家小公司的 Unix 系统管理员。真的，我是一名初级系统管理员，但我大部分时间都独自工作。我们是一个小型 IT 团队，只有我们三个人。我是 20 或 30 台 Unix 工作站和服务器的唯一系统管理员。另外两个支持 Windows 服务器和桌面。
+
+任何阅读这篇文章的系统管理员都不会惊讶地发现，作为一个不成熟的初级系统管理员，我最终在错误的目录中运行了 `rm` 命令。作为 root，我以为我正在为我们的某个程序删除一些陈旧的缓存文件。相反，我错误地清除了 `/ etc` 目录中的所有文件。糟糕。
+
+我意识到反了错误是看到了一条错误消息，`rm` 无法删除某些子目录。但缓存目录应该只包含文件！我立即停止了 `rm` 命令，看着我做了什么。然后我惊慌失措。一下子，无数个想法涌入了我的脑中。我刚刚销毁了一台重要的服务器吗？系统会发生什么？我会被解雇吗？
+
+幸运的是，我运行的是  `rm *` 而不是 `rm -rf *`，因此我只删除了文件。子目录仍在那里。但这并没有让我感觉更好。
+
+我立刻去找我的主管告诉她我做了什么。她看到我对自己的错误感到愚蠢，但是我犯的。尽管紧迫，她花了几分钟时间跟我做了一些指导。 她说：“你不是第一个这样做的人，在你这种情况下，别人会怎么做？”这帮助我平静下来并专注。我开始更少考虑我刚刚做的愚蠢事情，而更多地考虑我接下来要做的事情。
+
+我做了一个简单的策略：不要重启服务器。使用相同的系统作为模板，并重新创建 `/ etc` 目录。
+
+制定了行动计划后，剩下的就很容易了。只需运行正确的命令即可从另一台服务器复制 `/ etc` 文件并编辑配置，使其与系统匹配。多亏了我对所有东西都做记录，我使用现有的文档进行最后的调整。我避免了完全恢复服务器，这意味着一个巨大的中断。
+
+可以肯定的是，我从这个错误中吸取了教训。在接下来作为系统管理员的日子中，我总是在运行任何命令之前确认我所在的目录。
+
+我还学习了构建“错误策略”的价值。当事情出错时，恐慌并思考接下来可能发生的所有坏事是很自然的。这是人性。但是制定一个“错误策略”可以帮助我不再担心出了什么问题，而是专注于让事情变得更好。我仍然会想一下，但是知道我接下来的步骤可以让我“克服它”。
+
+--------------------------------------------------------------------------------
+
+via: https://opensource.com/article/18/7/my-first-sysadmin-mistake
+
+作者：[Jim Hall][a]
+选题：[lujun9972](https://github.com/lujun9972)
+译者：[geekpi](https://github.com/geekpi)
+校对：[校对者ID](https://github.com/校对者ID)
+
+本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
+
+[a]:https://opensource.com/users/jim-hall