Hmm.. i admit, i should've read the comments in the file i was editing.
But just a suggestion; you could have sudo keep a backup copy of the last known good for /etc/sudoers.
If it detects a corrupt /etc/sudoers, it tells you it's using the backup (and it's location).
That way, i as an app coder can focus on app coding instead of having to read the entire comments for every OS config file i need to edit, hoping to spot that comment that is going to save me from creating fatal errors by beginner mistake.
Serverconfig-ing is not my hobby, and it negatively affects my net income.
Hmm.. i admit, i should've read the comments in the file i was editing.
But just a suggestion; you could have sudo keep a backup copy of the last known good for /etc/sudoers.
If it detects a corrupt /etc/sudoers, it tells you it's using the backup (and it's location).
That way, i as an app coder can focus on app coding instead of having to read the entire comments for every OS config file i need to edit, hoping to spot that comment that is going to save me from creating fatal errors by beginner mistake.
Serverconfig-ing is not my hobby, and it negatively affects my net income.
The way it is now is very user-unfriendly.