Post, Mark K wrote:
That would mean that lstape (or at least the options you're giving it)
doesn't require root access. Not everything in /sbin or /usr/sbin
requires root access. For example, anyone can execute /sbin/ifconfig,
if all they do is display information.
Putting entries into /etc/sudoers doesn't grant root access unless the
user prefaces the command they want to issue with sudo. There's no way
every command could/would be changed to automatically check /etc/sudoers
when being called.
It's worth mentioning a couple of things here:
1. Suse sets up sudo differently. It can require the target user's
password, and that's how Suse configures it.
2. sudo gives direct access to all accounts, not just root.
Note, for my purposes that's fine, and it may be that sudo can be
configured to behave differently. The man page confuses me (I understand
the notation, but I have to think too hard).
Mark Post
-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Spann, Elizebeth (Betsie)
Sent: Thursday, October 19, 2006 6:26 PM
To: [email protected]
Subject: Re: CP commands through a Web interface
Hmm, I don't have to do "sudo lstape" for it to work but "sudo vmcp q v
da" does work.
Betsie
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
Please do not reply off-list
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
