Sponsored Content
Full Discussion: Change file owner
Special Forums Cybersecurity Change file owner Post 302543992 by DGPickett on Tuesday 2nd of August 2011 03:43:06 PM
Old 08-02-2011
Generally, root and admin ids use root as home, not application users. User and app files should not clutter root, they should be in dedicated sub-directories. Some users like to try to run flat with almost no directories, but that is not good practice. Usually, each user gets a /home/<user_name>/ home dir.

Groups can be created with groupadd, and users can be attached at creation time or later, but if the critical group is not the original, default group, the user may need to newgrp to change groups. If you have a user and files/dirs you want to share, their group you want on this id is on these files/dirs. If they are still inaccessible with matching groups, and you want this, "chmod -R g+rw <top_dir>" will ensure all have group read write on the whole sub-tree.

Last edited by DGPickett; 08-02-2011 at 04:50 PM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Can't change owner and group of a linux file

Hi, I don't know how the owner & group of a login file in redhat linux 7.2 changed to bache like, -rwxr-xr-x 1 bache bache 17740 Jun 20 02:05 login I am trying to change the owner and group to root by using #chown root login #chgrp root login But i am getting the error ... (7 Replies)
Discussion started by: bache_gowda
7 Replies

2. UNIX for Dummies Questions & Answers

Change owner

How to change the owner of group? -rw-r--r-- 1 lead lead Now I need to change LEAD to SUBLEAD.. how do I do this. I am using this command. $chown -R sublead test.lck I get this message chown: test.lck: Not owner I am logged in a LEAD.. All your help in regards are greatly... (16 Replies)
Discussion started by: venkyA
16 Replies

3. UNIX for Dummies Questions & Answers

How to change the owner of the file?

How to change the owner of the file? Can I change the owner of file/ files? I am user and not admin.(not logged as root) (1 Reply)
Discussion started by: redlotus72
1 Replies

4. UNIX for Dummies Questions & Answers

change owner of a file

im running into changing the ownership of a file. I am trying to change the ownership to "system", but it doesn't want to work. I sudo chown system /preferences.plist Password: chown: system: Invalid argument is there a way to read the ownership of a file, something like read chown... (3 Replies)
Discussion started by: CBarraford
3 Replies

5. UNIX for Dummies Questions & Answers

I am the owner,yet not allowed the change the ownership

sm860 IS the owner of the files below,but yet sm860 cannot change the ownership to bpt3a1.Please let me know why ? See below for details --- sm860@unixs741_DEV:/usr/gdp/home/ftp/bpt3a1/incoming/ahdb/T5/pcasav/daily $ ls -l pcasav* -rw-r--r-- 1 sm860 gdpintegrators 821 Sep 21 16:15... (8 Replies)
Discussion started by: MSHETTY
8 Replies

6. Shell Programming and Scripting

change owner

Dear All, i have a file and i want to change the owner of that file from another user. for example $ ls -l pkc.txt -rw-r--r-- 1 tdmscrdr dba 717 Nov 2 17:10 pkc.txt the owner of pkc.txt file is tdmscrdr and group is dba i want to change the owner of this file from... (7 Replies)
Discussion started by: panknil
7 Replies

7. Solaris

Owner of file gets 'not owner' error for chgrp

Hi Folks, I know that changing users and groups is pretty basic admin, but this one has got me stumped. When I try to change the group of a file for which I am the owner for, it still gives me a 'Not owner' error. For example, when I am logged in as 'webadmin', I have the following file: ... (4 Replies)
Discussion started by: brizrobbo
4 Replies

8. Shell Programming and Scripting

Change owner.

i want to find what are the files having owner as 'palani' my entire filesystem ( sub directories ) and needs to change the owner ( chown ) to 'raju'. Can anyone help on this to write a shell script. Thanks in advance. (3 Replies)
Discussion started by: senthil_is
3 Replies

9. Shell Programming and Scripting

How to change the owner of soft link

How to change the owner ship of the soft link lrwxrwxrwx 1 root root 4 Jun 29 16:27 soft_test -> test I need to change the above owner ship to httpd:httpd Whats the shell command i need to use for it :) (2 Replies)
Discussion started by: kalpeer
2 Replies

10. Solaris

Privileges : modify dir/file owner by other that's not owner

i need to do the following operations in solaris 10: 1.change owner and group owner for files which are not owned by the current user and user group 2.to can delete files in the /tmp directory which are not of the current user 3. allow to a standard user the deletion of files in the /tmp... (1 Reply)
Discussion started by: sirmark
1 Replies
SYSUSERS.D(5)							    sysusers.d							     SYSUSERS.D(5)

NAME
sysusers.d - Declarative allocation of system users and groups SYNOPSIS
/etc/sysusers.d/*.conf /run/sysusers.d/*.conf /usr/lib/sysusers.d/*.conf DESCRIPTION
systemd-sysusers uses the files from sysusers.d directory to create system users and groups at package installation or boot time. This tool may be used to allocate system users and groups only, it is not useful for creating non-system (i.e. regular, "human") users and groups, as it accesses /etc/passwd and /etc/group directly, bypassing any more complex user databases, for example any database involving NIS or LDAP. CONFIGURATION DIRECTORIES AND PRECEDENCE
Each configuration file shall be named in the style of package.conf or package-part.conf. The second variant should be used when it is desirable to make it easy to override just this part of configuration. Files in /etc/sysusers.d override files with the same name in /usr/lib/sysusers.d and /run/sysusers.d. Files in /run/sysusers.d override files with the same name in /usr/lib/sysusers.d. Packages should install their configuration files in /usr/lib/sysusers.d. Files in /etc/sysusers.d are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same path, the entry in the file with the lexicographically earliest name will be applied. All later entries for the same user and group names will be logged as warnings. If the administrator wants to disable a configuration file supplied by the vendor, the recommended way is to place a symlink to /dev/null in /etc/sysusers.d/ bearing the same filename. CONFIGURATION FILE FORMAT
The file format is one line per user or group containing name, ID, GECOS field description and home directory: #Type Name ID GECOS Home directory u httpd 440 "HTTP User" u authd /usr/bin/authd "Authorization user" g input - - m authd input u root 0 "Superuser" /root Empty lines and lines beginning with the "#" character are ignored, and may be used for commenting. Type The type consists of a single letter. The following line types are understood: u Create a system user and group of the specified name should they not exist yet. The user's primary group will be set to the group bearing the same name. The user's shell will be set to /sbin/nologin, the home directory to the specified home directory, or / if none is given. The account will be created disabled, so that logins are not allowed. g Create a system group of the specified name should it not exist yet. Note that u implicitly create a matching group. The group will be created with no password set. m Add a user to a group. If the user or group do not exist yet, they will be implicitly created. r Add a range of numeric UIDs/GIDs to the pool to allocate new UIDs and GIDs from. If no line of this type is specified, the range of UIDs/GIDs is set to some compiled-in default. Note that both UIDs and GIDs are allocated from the same pool, in order to ensure that users and groups of the same name are likely to carry the same numeric UID and GID. Name The name field specifies the user or group name. The specified name must consist only of the characters a-z, A-Z, 0-9, "_" and "-", except for the first character which must be one of a-z, A-Z or "_" (i.e. numbers and "-" are not permitted as first character). The user/group name must have at least one character, and at most 31. It is strongly recommended to pick user and group names that are unlikely to clash with normal users created by the administrator. A good scheme to guarantee this is by prefixing all system and group names with the underscore, and avoiding too generic names. For m lines, this field should contain the user name to add to a group. For lines of type r, this field should be set to "-". ID For u and g, the numeric 32-bit UID or GID of the user/group. Do not use IDs 65535 or 4294967295, as they have special placeholder meanings. Specify "-" for automatic UID/GID allocation for the user or group. Alternatively, specify an absolute path in the file system. In this case, the UID/GID is read from the path's owner/group. This is useful to create users whose UID/GID match the owners of pre-existing files (such as SUID or SGID binaries). The syntax "uid:gid" is also supported to allow creating user and group pairs with different numeric UID and GID values. The group with the indicated GID must get created explicitly before or it must already exist. For m lines, this field should contain the group name to add to a user to. For lines of type r, this field should be set to a UID/GID range in the format "FROM-TO", where both values are formatted as decimal ASCII numbers. Alternatively, a single UID/GID may be specified formatted as decimal ASCII numbers. GECOS A short, descriptive string for users to be created, enclosed in quotation marks. Note that this field may not contain colons. Only applies to lines of type u and should otherwise be left unset, or be set to "-". Home Directory The home directory for a new system user. If omitted, defaults to the root directory. It is recommended to not unnecessarily specify home directories for system users, unless software strictly requires one to be set. Only applies to lines of type u and should otherwise be left unset, or be set to "-". IDEMPOTENCE
Note that systemd-sysusers will do nothing if the specified users or groups already exist, so normally, there is no reason to override sysusers.d vendor configuration, except to block certain users or groups from being created. SEE ALSO
systemd(1), systemd-sysusers(8) systemd 237 SYSUSERS.D(5)
All times are GMT -4. The time now is 01:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy