I have problem giving user access to his public_html directory.
While when I am logged as root I can access my files by going to
where file.html is actually on this path...
But when user tries to access his file.html on this path....
it gets 404 error.
How would i fix this problem.Do I have to give some permission to user. Can you point me to some tutorial about this.
I havent done anything beside created user issuing this command
Thank you
Hi there,
I have a quick question about the UNIX command find, if you can help me I will appreciate it...
I am trying tho find a file which is under my 'public_html' directory.
As I know, I am making the command > find ~ -name filename(or directory name) to find the file or directory... (4 Replies)
I have two users, user1 and defaultuser. Whenever i logon to my unix session from a remote machine i log into defaultuser. Inside this "defaultuser" i have some setup files that i need to run from the other user that i have created myself i.e. "user1". The problem is even granting the ownership of... (3 Replies)
hi everyone.
iīve been burning my head for a week now with this problem and i couldnīt find a solution. iīve been looking for an answer in this forum but nothing either. so i decided to ask.
the thing is, i want to create a users with permission to kill just a group of users. i know how to write... (6 Replies)
Hello!
My web host has the public_html permission on my account set to 750.
1. Does this setting permit the world to use my submission forms
(contained within contact.html and purchase_order.html)?
2. The "0" entry looks like it blocks the public from conducting all activity
on my site.... (6 Replies)
Hi all,
I created testuser. by following command.
/usr/sbin/adduser -n test -d /disk05/collections/GET/testdata/
and then set its password by following command.
passwd testuser
When I login to system by testuser, it enters everything is ok.
The problem is how to set permission to this... (3 Replies)
Hello, I need to allow a user the ability to create files in a directory that is owned by another user/group. How can I do this? Thank you.
AIX version: 5.3.0.0
~David (4 Replies)
hello,
I would like to grant full access to a directory which is owned by root and the web application that created it. I have though of adding the permission to the whole world, but for security reason I would like to grant it to one more user.
I have tried this 'chmod -U newUser+wrx... (2 Replies)
Hi all,
Exactly like my title says.
I am learning PHP and MySQL and I used to use /var/www/ to host (contain or store) my files (.htm/.php) for testing. I could configure, finally, apache2 to use ~/public_html instead.
Now I when I tried to use $_SERVER it still directs (I used echo to show... (7 Replies)
Hello,
I have a a directory dir1 with permissions 700 (yes wantedly) and is owned by user1:group1
rwx------ user1 group1 dir1I need to give permissions to user2 (belongs to group2) on dir1 and its files, so I granted the permissions using setfacl ; instead of adding the user to groups and... (3 Replies)
Discussion started by: karumudi7
3 Replies
LEARN ABOUT HPUX
chroot
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)