Ken Gunderson wrote:

Which is useful in environments where you have jr. sysadmins, backup
operators, etc., i.e. different roles, not all of which you want/trust
to have full root access, so tasks can be limited to only those
necessary to fulfill that role.

On a boxes where I, or one or two others I know and trust, are the only
admin(s), I find sudo a complete pita and never use it.  When I want
root it's because I need to get something done and sudo just gets in my
way and adds unnecessary typing w/o any benefit - if I'm going to make a
typo or brain fart so bad as to blow up the box, sudo is not going to
save me.  Much better to actually have a # in your prompt and adhere to
the old sysadmin adage of sitting on your hands for 5 seconds before
hitting enter...

The point being here, that while sudo does have it's place, it's not the
magic bullet some would have us believe it is.

Agreed. In general, my first and only command (as myself) after logging in, is: 'sudo -i'.



_______________________________________________
OpenIndiana-discuss mailing list
[email protected]
http://openindiana.org/mailman/listinfo/openindiana-discuss

Reply via email to