chgrp -R | chmod +t sticky bit | chown --reference=file2 file1

By OK -
change the group of documents to editor
user1@ubuntu:~$ chgrp -R editor documents

 Sticky bit can protect these file from deletion. When sticky bit is set, only the owner or a user with root privileges can delete a file.
Additionally, sticky bit works only with directories and is ignored on ordinary files.

 
user1@ubuntu:~$ chmod +t documents
When user1 creates a file, the default permissions are limited to user1 and its private group (user1) named after the user account. This is the reason user2 sees Permission denied on editing file. By changing the group of documents to editor we allow all members of editor to read and write to files in documents.
To change ownership of a file, use the following command:
$chown newuser filename
To change the owner as well as the group of file, use the following command:
$chown newuser:newgroup filename
You can skip changing owner and change only the group with the following command:
$chown :newgroup filename
Note that the chown command can only be used by users with root privileges.

ubuntu@ubuntu:/home/us1$ ll
total 16
drwxr-xr-x 3 us1  us1group 4096 Dec 11 11:47 ./
drwxr-xr-x 9 root root     4096 Dec 11 11:38 ../
drwxr-xr-- 3 us1  us1group 4096 Dec 11 11:52 us1dir/
-rw------- 1 us1  us1group  608 Dec 11 11:47 .viminfo
ubuntu@ubuntu:/home/us1$ sudo chown ubuntu us1dir/
ubuntu@ubuntu:/home/us1$ ll
total 16
drwxr-xr-x 3 us1    us1group 4096 Dec 11 11:47 ./
drwxr-xr-x 9 root   root     4096 Dec 11 11:38 ../
drwxr-xr-- 3 ubuntu us1group 4096 Dec 11 11:52 us1dir/
-rw------- 1 us1    us1group  608 Dec 11 11:47 .viminfo

ubuntu@ubuntu:/home/us1$ chgrp -R ubuntu us1dir/
ubuntu@ubuntu:/home/us1$ ll us1dir/
total 16
drwxr-xr-- 3 ubuntu ubuntu   4096 Dec 11 11:52 ./
drwxr-xr-x 3 us1    us1group 4096 Dec 11 11:47 ../
-rw-r--r-- 1 us1    ubuntu      8 Dec 11 11:47 file1
drwxrwxrwt 2 us1    ubuntu   4096 Dec 11 11:55 stick/

How to pick owner/group information from a reference file?


chown --reference=[ref-file-name] [filename]
For example:
chown --reference=file2 file1

Comments

Post a Comment

Popular posts from this blog

HAproxy logging

By OK -
ubuntu@ubuntu:/etc/haproxy$ cat /etc/rsyslog.d/haproxy.conf # Create an additional socket in haproxy's chroot in order to allow logging via # /dev/log to chroot'ed HAProxy processes $ModLoad imudp $UDPServerRun 514 local0.* -/var/log/haproxy-0.log local1.* -/var/log/haproxy-1.log ### keep logs in localhost ## $AddUnixListenSocket /var/lib/haproxy/dev/log ------------------- ubuntu@ubuntu:/etc/haproxy$ cat /etc/haproxy/haproxy.cfg global chroot /var/lib/haproxy user haproxy group haproxy log 127.0.0.1   local0         log 127.0.0.1   local1 notice daemon frontend www     bind 192.168.40.128:8282    # haproxy public IP     default_backend as-backend    # backend used backend as-backend    balance leastconn    mode http  server as1 192.168.40.128:8082 check    # application srv 1 defaults log global mode http option httplog option dontlognull         contimeout 5000    
Read more

tomcat catalina coyote jasper cluster

By OK -
Tomcat Component are Catalina Coyote Jasper Cluster Catalina :  Catalina is the name of the servlet container of Apache Tomcat since version 4.x. Tomcat implements Sun Microsystems' specifications for servlet and JavaServer Pages (JSP), which are important Java-based Web technologies. Tomcat's servlet container was redesigned as Catalina in Tomcat version 4.x. other components of the Tomcat engine are: Tomcat Jasper which converts the code portions within JavaServer Pages into servlets and pass them to Catalina to process. Tomcat Coyote which is an HTTP connector based on HTTP/1.1 specifications that receives and transmits web requests to the Tomcat engine by listening to a TCP/IP port and returns requests back to the requesting client. Coyote :  The Coyote JK Connector element represents a Connector component that communicates with a web connector via the JK protocol (also known as the AJP protocol). This is used for cases where you wish to invisibly integr
Read more

NFS mount add in fstab _netdev instead of default | firewall-cmd --list-all

By OK -
Redhat recommends us to add  _netdev  option for NFS file system in /etc/fstab. So that they can be mounted after starting the networking service. Alternative ways to refer to partitions: Label : LABEL=label Network ID Samba : //server/share NFS : server:/share SSHFS : sshfs#user@server:/share Device : /dev/sdxy (not recommended) Example #1 //192.168.1.134/share_name /mnt/share_name cifs username=server_user,password=server_password,_netdev 0 0 ^ Path to your share ^ Mountpoint ^ Username ^ Password ^ See note A Note A: The  _netdev  options makes sure the mount is only attempted AFTER a network connection has been established. Example #2 10.10.10.1:/vol1/fs1 /data nfs defaults,_netdev 0 0 ============================ [root@localhost ~]# firewall-cmd --list-all public   target: default   icmp-block-inversion: no   interfaces:   sources:   services: dhcpv6-client high-availability ssh   ports:   protocols:   masquera
Read more