Other Help Topics :: sudo - /opt/sudoers - password - Linux question



I'm setting up a guest account on my machine and am removing the user's entry from /opt/sudoers.   I'm guessing that this is the way to remove a user's privileges for running sudo <command>.  It works... when I try to execute anything in console with the account, I get a friendly warning about being careful and a prompt for a password.

I've tried every password I can think of at the prompt, but have never been able to continue.  I've tried the password that I issued for the root account.  I've tried running sudo root and entering the same password to no avail.  I've tried other user accounts that I have set up with sudo privileges.

I have DSL 4.1 installed as multi-user.

Am I using the /opt/sudoer file properly? or should I have an entry in  there for the guest account with speciific pieces of information?

Much thanks,
John
Try the user's password.

An alternative to sudo would be su -c "some command"
Did you edit manually or with visudo?

Quote
CAVEATS

The sudoers file should always be edited by the visudo command which locks the file and does grammatical checking. It is imperative that sudoers be free of syntax errors since sudo will not run with a syntactically incorrect sudoers file.

When using netgroups of machines (as opposed to users), if you store fully qualified hostnames in the netgroup (as is usually the case), you either need to have the machine's hostname be fully qualified as returned by the hostname command or use the fqdn option in sudoers.
http://www.gratisoft.us/sudo/man/sudoers.html#caveats
You mean /etc/sudoers ?
Did you try this under the 'dsl' user?
What kind of installation?

Afaik DSL doesn't have visudo set up properly... you can first do `export EDITOR=vi` for example.
Yes, /etc/sudoers, sorry about that, still getting locations of things straight in my head.

No, I didn't know visudo existed.

When I used beaver, I removed the entire line for the user.  I just tried it with visudo (with the editor export) and it does act differently.  Now, I get the message that the 'user is not in sudo file'.  That's good.  And now I understand that I can su <user> to get the privileges in this session to work as a super-user... perfect!

Thanks for the link to the sudoers man page, I'll give it a good read.

Much thanks,
John
Next Page...
original here.