Skip to main content

Sticky Bit with example

Sticky Bit is used on folders in to avoid deletion of its content by users who are in same group with the owner of the file.

 Before understanding the sticky bit, I recommend reading SGID post which explains its disadvantage.
From SGID we understood that the user E1 can delete the file of E2 and vice versa.

 So to avoid this, we use sticky bit.

 Command

 To set:
chmod o+t <dir>

 To unset:
chmod o-t <dir>

eg:
# chmod o+t /project/
# ls -ld /project/
drwxrws--T. 2 root teamA 84 Aug 31 09:03 /project/

You will notice T in others permission.

Now the user E1 cannot delete file of E2 and E2 cannot delete of E1.

Below example shows E1 user trying to delete file of E2 but sticky bit didnt allow the file to get deleted.

$ rm e2_file.txt
rm: remove write-protected regular empty file ‘e2_file.txt’? y
rm: cannot remove ‘e2_file.txt’: Operation not permitted

 
Labels:

Comments

Post a Comment

Popular posts from this blog

Ansible script to stop iptables

 Ansible script to stop iptables and disable during boot Step 1. [root@cluster playbooks]# pwd /root/playbooks [root@cluster playbooks]# cat hosts [webservers] 169.254.41.221 169.254.41.222 Step2. [root@cluster playbooks]# cat iptables.yml --- - name: stop ipatbles and disable   hosts: webservers   tasks:   - name: stop iptables     service: name=iptables state=stopped   - name: disbale on iptable on boot     service: name=iptables enabled=no Step3: [root@cluster playbooks]# ansible-playbook iptables.yml PLAY [stop ipatbles and disable] *********************************************** TASK [setup] ******************************************************************* ok: [169.254.41.222] ok: [169.254.41.221] ok: [localhost] TASK [stop iptables] *********************************************************** changed: [localhost] ok: [169.254.41.221] ok: [169.254.41.222] TASK [disbale on iptable on boot] *********************************...
Post a Comment
Read more

Get information about remote hosts using Ansible

Get information about remote hosts using Ansible setup command Below command gives all the information of client hosts which includes memory, server architecture, IP adresses etc. [root@ansible mywork]# ansible all -i hosts -m setup If you need just memory information of remote node then for the above command need to add filter as shown below [root@ansible mywork]# ansible all -i hosts -m setup -a "filter=ansible_*_mb" node01 | SUCCESS => {     "ansible_facts": {         "ansible_memfree_mb": 873,         "ansible_memory_mb": {             "nocache": {                 "free": 919,                 "used": 77             },             "real": {                 "free": 873,           ...
Post a Comment
Read more

Using ansible ping module check connectivity between two nodes

Using ansible ping module check connectivity between two nodes Once server and client machine is configured with SSH passwordless authentication and  ansible installed in server, we will verify if ansible can connect from server to client. If you have not configured refer page Login to server node and create a directory to save all the work done in one location Eg:mywork [root@ansible ~]# mkdir mywork [root@ansible ~]# cd mywork/ Create new file called "hosts" under "mywork" and add your client host name in the file as shown below. [root@ansible mywork]# cat hosts [mynodes] node01 Now is the time to check if ansible from server machine able to communicate to client node01 To check this we will use ansible module called ping. Run command as shown below. [root@ansible mywork]# ansible all -i hosts -u root -m ping node01 | SUCCESS => {     "changed": false,     "ping": "pong" }
Post a Comment
Read more