Sponsored Content
Operating Systems Linux Red Hat Mkdir: cannot create directory `/home/phpmy/html': Permission denied centos Post 302800877 by jediwannabe on Tuesday 30th of April 2013 05:31:53 PM
Old 04-30-2013
yes you are right I need to do a chown phpmySmiliehpmy /home/phpmy.

thanks
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

ssh home directory permission

Hi All, I am using sftp to transfer files between two unix machines. As per my knowledge, in order to use public key authentication, the remote user's home directory permission should be set to 750 ( basically group and others should not have write permission ). Is there any way to over ride... (1 Reply)
Discussion started by: shihabvk
1 Replies

2. Shell Programming and Scripting

how to display the permission of the home directory

can anyone tell me how to display the permissions of a users home directory. can i use ls -l but it only gives the permissions of the files and directories inside the directory..:confused::confused::confused::confused: (9 Replies)
Discussion started by: nadman123
9 Replies

3. Solaris

Permission denied message for parent directory

Hi All, I have an issue that's eating my head for few days. I would appreciate if anyone could help me out in this to resolve this. In Solaris 8 container I am facing the below issue. As oracle user when I do ls -l in /dboracle mountpoint getting permission denied error messages. $ ls... (3 Replies)
Discussion started by: Sreerag446
3 Replies

4. UNIX for Advanced & Expert Users

about the access permission of users home directory

RHEL5.0 As we know, when root create a new user, a new home directory will be created : /home/user I want to know what determine the access permission of /home/user . Thanks! (1 Reply)
Discussion started by: cqlouis
1 Replies

5. UNIX and Linux Applications

mkdir: cannot create directory

Hi, I have network mount on two servers. One server I can create any directories without any issues, other server with the similar mount, I am not able to create directories starting with number! Creation, name start with a number: $ mkdir 1212 mkdir: cannot create directory `1212': No such... (12 Replies)
Discussion started by: ./hari.sh
12 Replies

6. Shell Programming and Scripting

[Solved] how to create multiple directory in one mkdir command

Hi, Unix Gurus, - I have a simple question, I need create multiple directory. I use mkdir {dir1, dir2, dir3) I got one directory as {dir1, dir2, dir3} I searched @ google, I got answer as above code.:wall::confused: Anybody has any idea Thanks in advance ---------- Post updated... (3 Replies)
Discussion started by: ken002
3 Replies

7. UNIX for Dummies Questions & Answers

mkdir: cannot create directory `/builds/somedir/': Permission denied

Hi, I am trying to run a shell script which contains an mkdir command as part of the execution. The script fails with the following error: mkdir: cannot create directory `/builds/somedir/': Permission denied The user running the script is 'harry' and belongs to group 'school'.... (5 Replies)
Discussion started by: Technext
5 Replies

8. Shell Programming and Scripting

mkdir home directory

Is there a way to create a directory in home directory through a bash script? And if yes then the files we want to put in there have to be put by the time is created in the bash script? (3 Replies)
Discussion started by: vlm
3 Replies

9. Shell Programming and Scripting

Trying to create a script to run as root, permission denied

Hello all, I am trying to create a script or a .command file that will run for me and my other techs on many, many Mac OSX computers that will add a file to the /etc/ folder called /etc/launchd.conf Every time I try to run the script, I get "Permission Denied" when trying to put the file into... (13 Replies)
Discussion started by: DonnieNarco
13 Replies
CHOWN(8)						    BSD System Manager's Manual 						  CHOWN(8)

NAME
chown -- change file owner and group SYNOPSIS
chown [-R [-H | -L | -P]] [-fhv] owner[:group] file ... chown [-R [-H | -L | -P]] [-fhv] :group file ... DESCRIPTION
chown sets the user ID and/or the group ID of the specified files. The options are as follows: -H If the -R option is specified, symbolic links on the command line are followed. (Symbolic links encountered in the tree traversal are not followed.) -L If the -R option is specified, all symbolic links are followed. -P If the -R option is specified, no symbolic links are followed. -R Change the user ID and/or the group ID for the file hierarchies rooted in the files instead of just the files themselves. -f Don't report any failure to change file owner or group, nor modify the exit status to reflect such failures. -h If file is a symbolic link, the owner and/or group of the link is changed. -v Cause chown to be verbose, showing files as they are processed. The -H, -L and -P options are ignored unless the -R option is specified. In addition, these options override each other and the command's actions are determined by the last one specified. The -L option cannot be used together with the -h option. The owner and group operands are both optional, however, one must be specified. If the group operand is specified, it must be preceded by a colon (``:'') character. The owner may be either a user name or a numeric user ID. The group may be either a group name or a numeric group ID. Since it is valid to have a user or group name that is numeric (and doesn't have the numeric ID that matches its name) the name lookup is always done first. Pre- ceding an ID with a ``#'' character will force it to be taken as a number. The ownership of a file may only be altered by a super-user for obvious security reasons. Unless invoked by the super-user, chown clears the set-user-id and set-group-id bits on a file to prevent accidental or mischievous creation of set-user-id and set-group-id programs. The chown utility exits 0 on success, and >0 if an error occurs. COMPATIBILITY
Previous versions of the chown utility used the dot (``.'') character to distinguish the group name. This has been changed to be a colon (``:'') character so that user and group names may contain the dot character. SEE ALSO
chflags(1), chgrp(1), find(1), chown(2), lchown(2), fts(3), symlink(7) STANDARDS
The chown command is expected to be POSIX 1003.2 compliant. The -v option and the use of ``#'' to force a numeric lookup are extensions to IEEE Std 1003.2 (``POSIX.2''). BSD
December 9, 2005 BSD
All times are GMT -4. The time now is 10:42 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy