Good morning,
From my support experience, it’s normally considered bad practice to run thing as root / (sudo) to force some of the permission, and we most of the times maintain the permission / ownership related to the Service User that most time have a limited set of permission ( Sudoer ) but still allows to run what is permitted.
But during the GIT challenges of the 100 Days feels like I have to do things a sudo to get it to be accepted… Is it a normal practice in different companies?
I’m just trying to understand if I’m biased due to my long tenure in my current company ( first and current 9y) practices or if the labs just took a easier approach to evaluate.
Thank you
Generally you’re correct: you don’t want to run servers as root unless you absolutely have to.
In the KKE and 100 Day labs, we want you, though, to be able to figure when you need or don’t need to use sudo. Some of the git related labs have git repos that are owned by root; some are owned by a regular user (say, natasha on the Storage Server). Knowing which is part of solving these problems.
Ok,
But with my bias in mind, everything should be converted to “natasha”.
And because of that I was getting some trouble getting the test to pass.
So, based on your explanation, I’m not solving it incorrect if I’m using sudo when the ownership belong to root, correct?
I’m just try to understand if my “passes”, mean that I really did it correctly, or I’m “forcing” my way through. You know what I mean?
But thank you for taking the time to help me.
Since the “conceit” of the KKE labs is that you’re doing it as part of a group, if you group prefers to have a directory owned by root, then the assumption is that it should stay that way 
So in the 100 Days or KKE labs, if it starts as root, generally speaking, we want you to do it as root.
1 Like