07-06-2011
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
well, I'm completely stumped so I'm hopeful that someone here may have an answer...one of my development machines is running Solaris 8 and I've been trying to create a folder in /apps. it gives me this message:
mkdir: Failed to make directory "*******"; Operation not applicable
I've tried... (2 Replies)
Discussion started by: jkrotz
2 Replies
2. UNIX for Advanced & Expert Users
Hi all,
I am using Sun Solaris 9 .In this system normal users unable to create files from the command line.I added these users in bin,adm and even root group i found them unable to create a file. (1 Reply)
Discussion started by: mallesh
1 Replies
3. UNIX for Advanced & Expert Users
Version-Release number of selected component (if applicable):
==================================================================
root@server # cat /etc/redhat-release
Red Hat Enterprise Linux ES release 4 (Nahant Update 5)
root@server # uname -a
Linux server.integrityserver.net... (16 Replies)
Discussion started by: fed.linuxgossip
16 Replies
4. Shell Programming and Scripting
Hi All,
I have directory under /opt/test.
The ownership of the test directory is root:root.
I have login to the server as test user.
I need to have some script to create a directory inside /opt/test.
This script will be called as test user.
When I try to execute... (4 Replies)
Discussion started by: kalpeer
4 Replies
5. Homework & Coursework Questions
first off let me introduce myself. My name is Eric and I am new to linux, I am taking an advanced linux administration class and we are tasked with creating a script to add new users that anyone can run, has to check for the existence of a directory. if the directory does not exist then it has... (12 Replies)
Discussion started by: pbhound
12 Replies
6. UNIX for Dummies Questions & Answers
I've tried to figure this out.
I'm only about 6 mos into my AIX admin duties, but I've got a "security" problem I can't figure out.
I've created a sub directory as follows:
drwx------ 2 root system 256 Apr 13 16:02 mike
I've logged in another session with the following user:
$ id... (2 Replies)
Discussion started by: mpheine
2 Replies
7. Solaris
Hi,
I am new to Solaris and when i am trying to Switch to root login from user, system throws message saying permissions denied...
Steps I Followed:
Created a user and logged into that user by SU username
tried to come back to root but system throws message "permissions denied"
... (7 Replies)
Discussion started by: VijaySolaris
7 Replies
8. UNIX for Advanced & Expert Users
Hi!! one strange problem occurred with my RHEL 5 box.
i'm having logs folder with ownership of non-root user. Created some files with root user under logs folder.
here is the scene:
-rw-r----- 1 root root 1048227 Feb 28 12:34 SystemOut_13.02.28_12.34.10.log
-rw-r----- 1 root root ... (6 Replies)
Discussion started by: sukhdip
6 Replies
9. UNIX for Dummies Questions & Answers
Is there any way to create a file in linux that root user also can't delete? (8 Replies)
Discussion started by: palani13dec
8 Replies
10. UNIX for Dummies Questions & Answers
Hi,
I tired changing password for mqm user in linux server with root user.
But still I couldn't able to login mqm user with changed password.
Can anyone please help on this.
# passwd mqm
Thanks,
Anusha (4 Replies)
Discussion started by: Anusha M
4 Replies
chroot(2) System Calls Manual chroot(2)
NAME
chroot() - change root directory
SYNOPSIS
DESCRIPTION
causes the named directory to become the root directory, the starting point for path searches for path names beginning with path points to
a path name naming a directory. The user's working directory is unaffected by the system call.
The entry in the root directory is interpreted to mean the root directory itself. Thus, cannot be used to access files outside the subtree
rooted at the root directory.
Security Restrictions
The effective user ID of the process must be a user with the privilege to change the root directory.
See privileges(5) for more information about privileged access on systems that support fine-grained privileges.
RETURN VALUE
returns the following values:
Successful completion.
Failure.
is set to indicate the error.
ERRORS
fails and the root directory remains unchanged if one or more of the following is true:
Any component of the path name is not a directory.
The named directory does not exist or a component of the
path does not exist.
The effective user
ID is not a user who has the privilege.
path points outside the allocated address space of the process. The reliable detection of this error is implementation
dependent.
The length of the specified path name exceeds
bytes, or the length of a component of the path name exceeds bytes while is in effect.
Too many symbolic links were encountered in translating the path
name.
WARNINGS
Obsolescent Interfaces
is to be obsoleted at a future date.
SEE ALSO
chroot(1M), chdir(2), privileges(5).
STANDARDS CONFORMANCE
TO BE OBSOLETED chroot(2)