On 21/10/10 20:31, Terry Coles wrote:
Hi,
Nearly all of the machines on my network were brought up to Kubuntu 10.10
using a clean installation, rather than an upgrade. Consequently, none had
samba installed or configured.
On this machine, I installed the package 'Samba' (system-config-samba), which
is a Gnome package that allows for very simple configuration, such as might be
used on a home network. It worked perfectly for me on this machine and
allowed me to set the workgroup, machine name and access rights very quickly.
On my son's machine it installed OK, but it won't let him start it. The
problem seems to be something to do with gksu. On this machine, gksu pops up
and asks for my password; on his machine it asks for the administrative
password, which isn't the same thing.
How do I get gksu to do a sudo instead of a su, and why is it different on two
apparently idenical installations?
Hi Terry,
It looks like gksudo is linked to gksu. If you run gksu with no
arguments, it normally prompts for the root password ( just like running
su ). However, Ubuntu disables root and the first user created in Ubuntu
is part of the admin group. Therefore sudo without an argument prompts
for the (first) users password.
Check his username is part of the admin group
groups user1
will list all groups for the user "user1"
Default sudoers file should be something like
# /etc/sudoers
Defaults env_reset
# User privilege specification
root ALL=(ALL) ALL
# Members of the admin group may gain root privileges
%admin ALL=(ALL) ALL
https://help.ubuntu.com/community/RootSudo
http://ubuntuforums.org/showthread.php?t=397398
John.
--
--------------------------------------------------------------
Discover Linux - Open Source Solutions to Business and Schools
http://discoverlinux.co.uk
--------------------------------------------------------------
--
Next meeting: Crown Hotel, Blandford Forum, Tuesday 2010-11-02 20:00
Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/
How to Report Bugs Effectively: http://goo.gl/4Xue