Sponsored Content
Operating Systems OS X (Apple) sudo chown -R `whoami` /usr/local Post 302534058 by chancho on Sunday 26th of June 2011 09:46:57 PM
Old 06-26-2011
Quote:
As a general rule, never change ownership of a system level directory, and definitely do not change that ownership recursively
Sounds like good advice. Thank You
 

10 More Discussions You Might Find Interesting

1. BSD

configure /usr/local/etc/be-agent.cfg

hi Howto configure Ralus at /usr/local/etc/be-agent.cfg on freeBSD 7.0 for Backup Exec 9.1? I've tried the following: # cat /usr/local/etc/be-agent.cfg name bsd.domain export / as root export /usr as usr export /var as var export /tmp as tmp force_address 10.10.1.50 tell... (0 Replies)
Discussion started by: ccc
0 Replies

2. Solaris

Questions about /usr/local/bin & scripts.

Hi gentlemen. For what intended is the directory /usr/local/bin? In this directory are some script. I don't understand how these scripts being in this directory are started. Each time after registration of the user occurs start of these scripts. These scripts start applications. (7 Replies)
Discussion started by: wolfgang
7 Replies

3. UNIX for Dummies Questions & Answers

/usr/local/lib is not searched by ld-linux.so by default?

it seems that /usr/local/lib is not searched by ld-linux.so by default in fedora14. If so, why some software put its lib files in /usr/local/lib? eg: glib and gtk+. (6 Replies)
Discussion started by: vistastar
6 Replies

4. UNIX for Dummies Questions & Answers

Difference between /opt and /usr/local.

Hello Gurus, Can any one explain me the difference between /opt and /usr/local. When should we use them. Can we link with any directory in windows I mean similarity between unix and windows. (7 Replies)
Discussion started by: rama krishna
7 Replies

5. AIX

/usr/local/bin/cvs: Not found

I can able to access /usr/local/bin/cvs in the terminal (AIX 6.1 Box). but i am getting the "/usr/local/bin/cvs: Not found " when i call it from the script. please some one assist me what maybe problem (6 Replies)
Discussion started by: hifirockz
6 Replies

6. Solaris

restrict sudo and chown in specified directory

Hi Dears, I have one requirement like this: general user A can execute command C with root privilege by sudo configuration some folders and files are created during the command C execution user A cannot access those folders and files because the owner is root user, so I want the user A... (0 Replies)
Discussion started by: crest.boy
0 Replies

7. Shell Programming and Scripting

/usr/local/bin/expr function not working

Legends, I am not able to set "expr" function in ksh script. Below is the sample code i used, and output is as "Syntax error" Please help me to come out of it. OUTPUT (9 Replies)
Discussion started by: sdosanjh
9 Replies

8. Shell Programming and Scripting

Chmod working in sudo run script but chown isn't

My git user has permission in sudoers to run a wrapper script to move files into my webroot. Everything is working fine except for the chown line. After the script has run, the files ar still root:root instead of apache:apache. Scratching my head...:confused: #!/bin/sh echo echo "****... (4 Replies)
Discussion started by: dheian
4 Replies

9. Fedora

Clueless re Java: /opt vs. /usr/local

It seems this is a oft debated item, that's over my head. So here's what I've got: Java 7 set up at /opt/ but I really want it at /usr/local... What have I done? Have: Debian 7 (whezzy) with gnome, so what do I do to set things back where it should be? I guess this is a hot topic... (3 Replies)
Discussion started by: sas
3 Replies

10. BSD

FreeBSD: /usr/bin/ld not looking in /usr/local/lib

I'm not sure if this is the default behavior for the ld command, but it does not seem to be looking in /usr/local/lib for shared libraries. I was trying to compile the latest version of Kanatest from svn. The autorgen.sh script seems to exit without too much trouble: $ ./autogen.sh checking... (2 Replies)
Discussion started by: AntumDeluge
2 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 12:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy