It is quite simple. A few examples should clarify it for you.
You can grant users jelo and kiki full access to all privileged commands, with this /etc/sudoers entry.
Code:
jelo, kiki ALL=(ALL) ALL
This is generally not a good idea because this allows jelo and kiki to use the su command to grant themselves permanent root privileges thereby bypassing the command logging features of sudo.
A better way is to grant access to specific program files. For example, this /etc/sudoers entry allows user jelo and all the members of the group operator to gain access to all the program files in the /sbin and /usr/sbin directories, plus the command /opt/oracle/check.pl. BTW, the trailing slash (/) is required to specify a directory location:
folks;
How can i give a group a sudo permission to execute only some command "like start/stop Apache", so every user in that group can sudo to use this as himself, i mean when he tries to sudo, he will be asked for a password (and make it so he must use his own NT password not a generic one) then... (6 Replies)
Hi,
I'm one of a server administrators. I've the linux root account but I don't know the root password of MySQL (Server version: 5.0.32). I want to GRANT ALL PRIVILEGES to my MySQL account without changing the MySQL's root password. How can I do so? (0 Replies)
HI friends can i know how to assign sudo permission to normal user in solaris, and if not i want to assign few commands like format,user creation to normal user, i want to share few permission to normal user towork like a root in $ prompt. (2 Replies)
HI All,
I am using solaris
i created a user adam and updated his permissions
in vi sudoers file as follows
adam ALL=(ALL) NOPASSWORD: ALL
...........
when i create user by logging as sudo user .
$ sudo useradd -d /home/kalyan -m -s /bin/sh kalyan
sudo: not found
... (6 Replies)
Hi,
I'm trying to provide "/usr/bin/kill -HUP" command to one of the user using sudo file. I have configured sudo as following:
$cat /etc/sudoers
User_Alias AA=conadmin
Cmnd_Alias KILL1=/usr/bin/kill -HUPAA ALL=NOPASSWD:KILL1
When I login as the user and execute 'sudo -l' command, it... (2 Replies)
All:
I'm having a problem with sudo on Solaris 5.10 that is giving me fits (and BTW, I'm a Linux admin by trade...).
The issue is that I have a number of users (myself included) that cannot sudo to root to complete user admin tasks. Assuming the user is jdoe, and the group with the elevated... (3 Replies)
Hi All
I had installed sudo in HP UX 11.3 and it is working fine but not able to make entry required to set permission similar to ROOT without using password (PASSWD) change option for define user in /etc/sudoers file
Please help if some know the syntex? :confused::wall: (2 Replies)
I have a script that checks if the script has been ran with sudo.
If the script is not ran as sudo, the current script is being executed with exec sudo bash.
You are asked for a password, you type in the password, success. Everything is perfect - the commands inside the script are ran as sudo.... (1 Reply)
Hi,
I need to grant read permission to a normal user on sulog file on AIX 6.1.
As root I did acledit sulog and aclget shows "extended permissions" as "enabled" and normal user "splunk" has read permissions. When I try to access sulog as splunk user it won't allow and aclget for splunk user... (6 Replies)
Discussion started by: prvnrk
6 Replies
LEARN ABOUT OSF1
undohash
dohash(8) System Manager's Manual dohash(8)NAME
dohash, undohash - Hashes or unhashes IMAP configuration directories
SYNOPSIS
/usr/sbin/dohash [-f] [-h] [-i]
/usr/sbin/undohash
OPTIONS
The following options are available only for the dohash command: Forces the hashing process to continue even if the command encounters
errors. Prints a usage message for the command. Runs the hashing process interactively.
DESCRIPTION
The dohash command converts the IMAP configuration directories from the format for older versions of the Cyrus IMAP4 Revision 1 server to
the new format for Version 1.6.1 or higher.
Starting with Version 1.6.1 of the server, the IMAP user files in the quota and user directories are stored in a through z subdirectories,
sorted by the first character of each user name. This arrangement reduces the number of entries in a given directory and consequently
increases performance and scalability. The dohash command creates the a through z subdirectories and sorts the existing IMAP files as
described; the undohash command reverses this process, in case you need to revert to a previous version of the server.
You can optionally sort the users' directories in the IMAP mail spool in the same manner if you enable the hashimapspool option in the
/etc/imapd.conf file before invoking the dohash command. See imapd.conf(4) for more information.
Note that you must be logged in as the imap user to use the dohash command; otherwise, the newly-created subdirectories will not have the
proper ownership.
EXAMPLES
The following example shows output from the dohash command: # /usr/sbin/dohash configuration directory /var/imap... hashing user directory
hashing quota directory done hashing
In this example, the configuration directory is /var/imap; therefore, you could check that the dohash command has successfully hashed the
directories by using the ls command as follows: # ls /var/imap/quota /var/imap/user /var/imap/quota: a b c d e f g h i j k l m
n o p q r s t u v w x y z
/var/imap/user: a b c d e f g h i j k l m n o p q r s t u v w x y z
The slash () indicates line continuation.
FILES
Configuration file for the IMAP server. Specifies the location of the IMAP configuration directory.
SEE ALSO
Commands: imapd(8)
Files: imapd.conf(4)
Network Administration
dohash(8)