12-05-2008
Then you need to add the "control" user to sudo and give your users the "control" account password. If they need to sudo commands as the "control" user and you want a sudo shell then just sudo to root [or use Solaris profiles].
In short: no, what you're asking is not possible as requested.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I want the user to be able to commands as another user.. but when they do that.. I need them to have the environment variables of the other user. is this possible with sudo?
sudo -H -u user env
'env' is giving me the environment of the current user, not the user I want to run commands as.
... (1 Reply)
Discussion started by: julesdiane
1 Replies
2. Linux
Hi everyone,
I wonder if anyone ever came across the idea of unifying AD and Linux user accounts
We have a Linux machine with 'samba' 'winbind' service configured to let Windows AD users to logon locally using their AD accounts and passwords.
I can use 'su' to get to the local user privilege... (0 Replies)
Discussion started by: will_mike
0 Replies
3. UNIX for Dummies Questions & Answers
I want to check if in a host a set of persons have sudo access or not and I dont have root access to the host. (1 Reply)
Discussion started by: pristine
1 Replies
4. UNIX for Advanced & Expert Users
I am running a serverapplication on a HP-UX machine where I need to handle some of the commands as a specified user called "druser".
When I log on as this user with the command;
sudo -u druser -sit starts an instance of the shell as that user.
However, it doesn't load that users .profile from... (1 Reply)
Discussion started by: ukiome
1 Replies
5. Shell Programming and Scripting
Hi all,
I have to create SSH public key for multiple users.
Iam creating a script in which, through root, I have to switch to multiple accounts to create SSH keys and then transfer it to the respective servers.
First I tried with single user id and everything worked fine.
When I try to sudo... (1 Reply)
Discussion started by: deepakwins
1 Replies
6. Shell Programming and Scripting
I am writing a BASH script to update a webserver and then restart Apache. It looks basically like this:
#!/bin/bash
rsync /path/on/local/machine/ foo.com:path/on/remote/machine/
ssh foo.com sudo /etc/init.d/apache2 reloadrsync and ssh don't prompt for a password, because I have DSA encryption... (9 Replies)
Discussion started by: fluoborate
9 Replies
7. Shell Programming and Scripting
Hello all,
Hope you all are doing good :).
First of all, I apologize for my bad English
I want to get list of all user that have 'sudoCommand: ALL'
I've tried different sed and awk combinations without success :wall:
the command for extracting the OU for sudo is:
ldapsearch -x... (4 Replies)
Discussion started by: corky
4 Replies
8. UNIX for Dummies Questions & Answers
Hi Everyone,
When I runthe query in ssh shell sudo cat /etc/security/user , I see half of the users cut down from the display screen. what I want to do is using the somthing like "pop" that when I hit the enter key every time the screen should move to the next user? does some one has any idea how... (4 Replies)
Discussion started by: starter2011
4 Replies
9. Red Hat
All,
I need to disable "sudo -i" and "su - " for all servers in our environment, We want to make sure no one run commands or delete files across environment using switching to root account. can you guys please lets me know if this is achievable.
Thanks and Regards
shekar (2 Replies)
Discussion started by: shekar777
2 Replies
10. Solaris
Hi,
I always use "sudo -U user -l" as root and it gives me list of sudo access, that person have. But on one Solaris server, I can't run it. recently only I installed latest patchset on this server. Not sure, if that changed something on this. However, sudo package is showing old one.
# id -a... (1 Reply)
Discussion started by: ron323232
1 Replies
LEARN ABOUT OPENSOLARIS
gksu
GKSU(1) General Commands Manual GKSU(1)
NAME
gksu - a Gtk+ su frontend
SYNOPSIS
gksu [ options ] <command>
gksudo [ options ] <command>
DESCRIPTION
This manual page documents briefly gksu and gksudo
gksu is a frontend to su and gksudo is a frontend to sudo. Their primary purpose is to run graphical commands that need root without the
need to run an X terminal emulator and using su directly.
OPTIONS
These programs follow the usual GNU command line syntax, with long options starting with two dashes (`-'). A summary of options is
included below.
Common Options:
--user <user>, -u <user>
Calls <command> as the specified user
--message <message>, -m <message>
Replaces the standard message shown to ask for password for the argument passed to the option
--sudo-mode, -S
Use sudo instead of su as backend authentication system. Notice that the X authorization magic will not work when using sudo for
target users other than root.
--title <title>, -t <title>
Replaces the default title with the argument
--icon <icon>, -i <icon>
Replaces the default window icon with the argument
--print-pass, -p
Asks gksu to print the password to stdout, just like ssh-askpass. Useful to use in scripts with programs that accept receiving the
password on stdin.
--disable-grab, -g
Disables the "locking" of the keyboard, mouse, and focus done by the program when asking for password
--ssh-fwd, -s
Strip the host part of the $DISPLAY variable, so that GKSu will work on SSH X11 Forwarding.
--login, -l
Makes this a login shell. Beware this may cause problems with the Xauthority magic. Run xhost to allow the target user to open win-
dows on your display! This is ignored if running with sudo as backend for authentication.
--preserve-env, -k
Preserve the current environments, does not set $HOME nor $PATH, for example.
FILES
/etc/gksu.conf
Configuration file to setup system-wide defaults for gksu/gksudo. It provides an option to force the display grabing, also.
RETURN VALUE
On success, gksu will return 0. If an authentication error ocurred, it will exit with error code 3. If the user canceled the dialog or
closed the window, it will return error code 2. On other error conditions, gksu will return 1.
NOTE
Note that <command> and all its arguments should be passed as one single argument to gksu just like one would to when using su.
SEE ALSO
su(1), gksuexec(1).
AUTHOR
This manual page was written by Gustavo Noronha Silva <kov@debian.org> for the Debian GNU/Linux system (but may be used by others).
2003 GKSU(1)