Peter, That is a good suggestion if the application was not meant for mass deployment. Otherwise each machine's sudoers file would have to be edited accordingly, which would be a bummer for users that do not know how to do so. And that is likely the majority of Mac users. I would venture to say that the majority of Mac users never even opened the Terminal.
The solution is elegant, I believe, in that it will work on any Mac OS X machine and takes advantage of Bash' s flexibility with Rev's shell structure. Happy coding! - Justin On Sat, Jun 12, 2010 at 12:11 PM, Richmond <richmondmathew...@gmail.com> wrote: > On 06/12/2010 12:08 PM, Peter Alcibiades wrote: >> >> Is there a reason you cannot use the NOPASSWD option in sudo? Maybe this >> is >> not how it works in OSX, but what you'd normally do is to edit >> /etc/sudoers >> to allow this particular user to perform this particular command with the >> no >> password option, and its done. If you do this, the command can be limited >> to one with specific options. For instance, you can allow shutdown with >> the >> -h option, but not the -r option. No-one has to know the root password >> then >> and it is not written anyplace. Yes, you do have to know it to edit >> /etc/sudoers. >> > > This is all very charming, but I wonder how one would > effect this from a standalone on an end-user's machine . . . :) > _______________________________________________ > use-revolution mailing list > use-revolution@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution > _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution