02-18-2012
Basically, only root should be running the administrative commands in /sbin and /usr/sbin. Non-root users may be technically able to run them - according to the file permissions - but many times the command will fail because the user does not have sufficient access to some resource that the command requires, such as the /proc or /dev filesystems. If you want to empower specific users to run specific commands as root, then set up sudo and use that.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello All,
hope someone here can help me with this. I am a new unix system administrator on the HP-UX machine. Every night, our operators back up our file system using one tape but as of recently, our files have gotten bigger and it now requires 2 tapes for a complete backup. Since the operators... (3 Replies)
Discussion started by: sanjit
3 Replies
2. UNIX for Dummies Questions & Answers
All,
I want to run a non-root script as the root user with non-root environment variables with crontab. The non-root user would have environment variables for database access such as Oracle or Sybase. The root user does not have the Oracle or Sybase enviroment variables. I thought you could do... (2 Replies)
Discussion started by: bubba112557
2 Replies
3. UNIX for Dummies Questions & Answers
Hi
I'm wondering how I can find all the files which were installed on certain date?
For example: I'm looking for alle the files which were installed on the 11.09.06 on the system.
Does somebody know how to do this?
Thanks
Reto (2 Replies)
Discussion started by: goldenglobe
2 Replies
4. UNIX and Linux Applications
I have a shell script. In this script I executes various command and my requirement is such that if any command fails I've to terminate the shell script.
To achieve this objective I'm checking the value of $? after each command and if its value is greater thaen I 'exit' the script.
Is there... (2 Replies)
Discussion started by: ashok2008
2 Replies
5. AIX
Hi I am new to AIX and any help regarding the same would be really appriciated, thanks In advance.
My priority issue is how to detect from command line that the volume / disk on AIX machine is a USB or removable disk /volume
and if possible can we list out details for that disk / volume (1 Reply)
Discussion started by: mak_mailbox
1 Replies
6. Shell Programming and Scripting
I need to know a command to find out which version of Perl Im currently running.
Thanks
Ben (2 Replies)
Discussion started by: bigben1220
2 Replies
7. Solaris
Hi All
After downloading ZFS documentation from oracle site, I am able to successfully migrate UFS root FS without zones to ZFS root FS. But in case of UFS root file system with zones , I am successfully able to migrate global zone to zfs root file system but zone are still in UFS root file... (2 Replies)
Discussion started by: sb200
2 Replies
8. Shell Programming and Scripting
i have this line of code on a korn shell script to detect the presence of script run:
ISRUNNING=`ps -eaf -o args | grep -i sfs_load_file.ksh | grep -v grep | wc -l`
sometimes this returns either 1, 2, or 3. when it returns 2 or 3 that tells us that there are more than 1 script of... (8 Replies)
Discussion started by: wtolentino
8 Replies
9. Shell Programming and Scripting
Hello,
I am running a python file from terminal and I wish to see which code is running at background. When I use htop, I see just a few commands, unable to see entire command.
htop > report
nano report
Output:
^
Following parts of ffmpeg line is not shown by htop. Just showing... (7 Replies)
Discussion started by: baris35
7 Replies
10. Ubuntu
I am trying to find a way to run a command upon any movement of a mouse.
The 1st statement shows the mouse co-ordinates. So it can detect mouse movement.
xinput test 9
First list input devices:
$ xinput list
If possible, I would like to use it in a bash script. (2 Replies)
Discussion started by: drew77
2 Replies
chroot(8) System Manager's Manual chroot(8)
NAME
chroot - Changes the root directory of a command
SYNOPSIS
/usr/sbin/chroot directory command
DESCRIPTION
Only root can use the chroot command. The chroot command changes the root directory from / to the specified directory when the command
executes. (The command specified includes both the command name as well as any arguments.) Consequently, the root of any path (as indicated
by the first / (slash) in the pathname) changes to directory and is always relative to the current root. Even if the chroot command is in
effect, directory is relative to the current root of the running process.
Several programs may not operate properly after chroot executes. You must ensure that all vital files are present in the new root file
system and the relevant pathnames for the files map correctly in the new root file system.
For example, the ls -l command fails to give user and group names if the new root file system does not have a copy of the /etc/passwd and
/etc/group files. If the /etc/passwd and /etc/group files in the new root file system represent different user and group names, then the
output from the ls -l command will be based on those names, not the ones for the system's own name database. Utilities that depend on
description files produced by the ctab command may also fail if the required description files are not present in the new root file system.
The chroot program uses the execv() function to invoke the specified command. As a consequence, the command specified must be an exe-
cutable binary, not a shell script. Further, if the program requires indirect loading (for example, due to unresolved symbols requiring
use of a shared library), then /sbin/loader as well as any files it requires (for example, shared libraries) must be present in the new
root file system in the appropriate locations.
EXAMPLES
To run a subshell with another file system as the root, enter a command similar to the following. Note in this example, the file system is
on the /dev/disk/dsk13a device and is mounted to /mnt/dsk13a: chroot /mnt/dsk13a /sbin/sh The command shown in the previous example spec-
ifies a change from the current root file system to the one mounted on /mnt/dsk13a while /sbin/sh (which itself is relative to the new root
file system) executes. When /bin/sh executes, the original root file system is inaccessible. The file system mounted on /mnt/dsk13a must
contain the standard directories of a root file system. In particular, the shell looks for commands in /sbin, /bin, and /usr/bin (among
others) on the new root file system.
Running the /sbin/sh command creates a subshell that runs as a separate process from the original shell. Press to exit the subshell and
return to the original shell. This restores the environment of the original shell, including the meanings of the current directory (.) and
the root directory (/). To run a command in another root file system and save the output on the initial root file system, enter a command
similar to the following. Note in this example, the file system is on the /dev/disk/dsk13a device and is mounted to /mnt/dsk13a:
chroot /mnt/dsk13a /bin/cc -E /u/bob/prog.c > prep.out
The previous command runs the /bin/cc command with /mnt/dsk13a as the specified root file system. It compiles the /mnt/dsk13a/u/bob/prog.c
file, reads the #include files from the /mnt/dsk13a/usr/include directory, and puts the compiled text in the prep.out file on the initial
root file system. To create a file relative to the original root rather than the new one, use this syntax and enter:
chroot directory command > file
CAUTIONS
If special files in the new root have different major and minor device numbers than the initial root directory, it is possible to overwrite
the file system.
FILES
Specifies the command path.
RELATED INFORMATION
Commands: cc(1), cpp(1), ls(1), sh(1)
Functions: chdir(2), chroot(2) exec(2) delim off
chroot(8)