On Sat, 3 Sep 2011 19:48:33 -0400 Stephen Allen <[email protected]> wrote:
> On Sat, Sep 03, 2011 at 11:32:00AM +0000, darkestkhan wrote: > > 2011/9/3 Stephen Allen <[email protected]>: > > > > It contains just 2 fields; > > > > > > # User privilege specification > > > root ALL=(ALL:ALL) ALL > > > > > > # Allow members of group sudo to execute any command > > > %sudo ALL=(ALL:ALL) ALL > > > > > > > /etc/sudoers contains informations about who has rights to access > > root level privileges (though I know it can do much more, like > > giving only limited privileges) > > > > at the bottom of /etc/sudoers you should have this line: > > username ALL=(ALL) ALL > > > > where username is the name of user that will have root level > > privileges, so in my case it is like this: > > darkestkhan ALL=(ALL) ALL > > > > > > You will probably have to run in maintenance (or rescue, forgot how > > it was called) mode, after that (or reboot) everything should work > ---end quoted text--- > > Cool. Thanks for the help. > > Strange why that line isn't there aye? > > Sudo in sid has just been updated to a version with a different sudoers file format. Those who opted for a new configuration file got the empty one quoted above, those who opted to keep theirs kept their own additions to the old one. The latter also ended up with a sudo which couldn't see sbin and the lower level sbins, which then stopped further updates from working under sudo... possibly a changelog would have been in order? The clean new sudoers was also provided (as the .dpkg-dist file), so it wasn't too hard to combine the two (clue: the Defaults secure_path configuration is necessary to restore the path to include the sbins). -- Joe -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
