Normally a home directory is fully owned by the user, and you can do
Code:
chown -hR username /home/username
The -h is necessary because by default chown follows a symbolic link. Imagine the user has a symlink mypasswd -> /etc/passwd ...
If you want to be safe then use "find" to only change owner to "username" if current owner is "olduser".
Im trying to simply share a directory on one unix server and mount that share on a different unix server.
There is no "share" command like on sun. What is the command to create a share on HP-UX? (2 Replies)
Sometimes you get the tiger...but sometimes he get you and this latest home network “project” of mine has gnawed on me pretty badly. Perhaps you can offer some technical help. It will be heartily appreciated.
I have a small home network initially comprising two computers running Windows... (1 Reply)
Hi,
Im running 32-bit solaris on sparc. We have a NAS(Network attached drive), with its IP address, username and password.
I'd like to be able to mount it on the solaris machine, and unmount it.
The best possibility would be able to mount it simulataneously on 2 or more systems.
Please... (9 Replies)
Hi,
I have two machines. M1 and M2 and having a generic id catadm, these two machines having common mount of /u/catadm directory.
with this setup, ssh autologin is failing for me and asking me to enter password when i try autologin using this generc id from M1 to M2
catadm-M1$ ssh... (3 Replies)
Hi,
I recently added a disk on a solaris 9 and I wanted to make it accessible for another machine, using the same name
here is what i did :
On the machine holding the internal disk
in vfstab i added the line
/dev/dsk/c1t1d0s4 /dev/rdsk/c1t1d0s4 /SHARED2 ufs 2 yes ... (2 Replies)
Hi,
I am having some NFS directory consistency problems with the below setup on a local (192.) network:
1. Different permissions (chmod) for the same NFS dir are reflected on different clients.
2. (more serious) an NFS dir created on client1 cannot be accessed on client2; this applies to some... (10 Replies)
Discussion started by: cosmojetz
10 Replies
LEARN ABOUT FREEBSD
chown
CHOWN(8) BSD System Manager's Manual CHOWN(8)NAME
chown -- change file owner and group
SYNOPSIS
chown [-fhvx] [-R [-H | -L | -P]] owner[:group] file ...
chown [-fhvx] [-R [-H | -L | -P]] :group file ...
DESCRIPTION
The chown utility changes the user ID and/or the group ID of the specified files. Symbolic links named by arguments are silently left
unchanged unless -h is used.
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. This is the default.
-R Change the user ID and/or the group ID of the specified directory trees (recursively, including their contents) and files. Beware of
unintentionally matching the ``..'' hard link to the parent directory when using wildcards like ``.*''.
-f Do not report any failure to change file owner or group, nor modify the exit status to reflect such failures.
-h If the file is a symbolic link, change the user ID and/or the group ID of the link itself.
-v Cause chown to be verbose, showing files as the owner is modified. If the -v flag is specified more than once, chown will print the
filename, followed by the old and new numeric user/group ID.
-x File system mount points are not traversed.
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 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 numeric user ID or a user name. If a user name is also a numeric user ID, the operand is used as a user name. The
group may be either a numeric group ID or a group name. If a group name is also a numeric group ID, the operand is used as a group name.
The ownership of a file may only be altered by a super-user for obvious security reasons.
EXIT STATUS
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.
On previous versions of this system, symbolic links did not have owners.
The -v and -x options are non-standard and their use in scripts is not recommended.
SEE ALSO chgrp(1), find(1), chown(2), fts(3), symlink(7)STANDARDS
The chown utility is expected to be IEEE Std 1003.2 (``POSIX.2'') compliant.
HISTORY
A chown utility appeared in Version 1 AT&T UNIX.
BSD February 21, 2010 BSD
09-26-2018
