10-10-2008
You can use sudo to allow them execute commands as UID 0 or you can edit the passwd file and make their UID 0 as well.
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi All,
Oracle 8.0 database is running on SCO-UNIXWARE 7.0 Operating system. Some how ORACLLE DATABASE has crashed. After rebooting the PC only the SUPER USER could login. No other user is able to login.
we need ORACLE user to start the DATABASE again.
It is asking for the password, after... (2 Replies)
Discussion started by: konda
2 Replies
2. Shell Programming and Scripting
Good day Guys!!!
I am currently making a script in AIX, the script runs a SAS job, the owner of the script is the root, but the SAS jobs cannot be run by the root, as it should be run by a user 'sasia'. But inside the script, root creates a logfile, so what I need is just to su to sasia for the... (3 Replies)
Discussion started by: sasia
3 Replies
3. AIX
I'm trying to give a non-root user the right to start IBM HTTP Server, the web server is listening on port 80, but for AIX, ports under 1024 are privilege ports which can be used only by root.
/usr/IBMIHS/bin# ./apachectl start
(13)Permission denied: make_sock: could not bind to address :::80... (1 Reply)
Discussion started by: ibmer414
1 Replies
4. Shell Programming and Scripting
Hi all,
I am trying to eject the cdrom from a livecd after certain stage...
Now assuming that it is possible to eject,please consider my issue!!!
The OS boots into a regular user by default...so i am unable to use the eject command to push out the drive...
However if i try pfexec eject it... (3 Replies)
Discussion started by: wrapster
3 Replies
5. Linux
Hi,
Is it possible to grant root privileges to an ordinary user?
Other than 'sudo', is there some way under Users/Groups configuration?
I want ordinary user to be able to mount, umount and use command mt.
/Brendan (4 Replies)
Discussion started by: brendan76
4 Replies
6. UNIX for Dummies Questions & Answers
Does anyone know if this is possible?
I want to give some users access to root's crontab but only with a read privilege.
Is this possible to do or can only root or people with full root sudo view root's cron? (4 Replies)
Discussion started by: LordJezoX
4 Replies
7. Solaris
I've come across this question during interview as Sys Adm.
"How you reset lost root/superuser password on x86 system running solaris (8/9/10) which remotely located. (Not locally in front of you)"
As much as I know, you must be physically in front of the server to reset the lost... (4 Replies)
Discussion started by: shahru
4 Replies
8. Solaris
Hi,
It's actually strange, but Is there any way through which I can assign super user rights to normal user.
Actually su/sudo/rbac does solve these but switching id is the problem for an application.
For eg: $dladm show-dev
insufficient priviliges.
Is there any way to get it done ?
... (8 Replies)
Discussion started by: tuxian
8 Replies
9. Shell Programming and Scripting
Currently in my system Red Hat is installed. And Many user connect to my machine via SSH Techia Terminal.
I want to give some users a root level access.
Can anyone please help me how to make it possible. I too searched on the Google but didn't find the correct way
Regards
ADI (4 Replies)
Discussion started by: adisky123
4 Replies
LEARN ABOUT ULTRIX
chroot
chroot(2) System Calls Manual chroot(2)
Name
chroot - change root directory
Syntax
chroot(dirname)
char *dirname;
Description
The dirname is the address of the pathname of a directory, terminated by a null byte. The system call causes this directory to become the
root directory (/).
For a directory to become the root directory, a process must have execute (search) access to the directory.
This call is restricted to the superuser.
Return Values
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and errno is set to indicate an error.
Diagnostics
The system call fails and the root directory is unchanged under the following conditions:
[ENOTDIR] A component of the dirname is not a directory.
[ENAMETOOLONG] A component of a dirname exceeded 255 characters, or an entire dirname exceeded 1023 characters.
[ENOENT] The dirname argument points to the name of a directory which does not exist, or to an empty string and the environment
defined is POSIX or SYSTEM_FIVE.
[EFAULT] The dirname points outside the process's allocated address space.
[ELOOP] Too many symbolic links were encountered in translating the pathname.
[EIO] An I/O error occurred while reading from or writing to the file system.
[ESTALE] The file handle given in the argument is invalid. The file referred to by that file handle no longer exists or has been
revoked.
[ETIMEDOUT] A connect request or remote file operation failed because the connected party did not properly respond after a period of
time that is dependent on the communications protocol.
[EPERM] The effective user ID is not that of superuser.
See Also
chdir(2)
chroot(2)