NFS device is busy Not able to umount

This is not advised always

# umount /nfs_apps

umount: /nfs_apps: device is busy
umount: /nfs_apps: device is busy

Try the below commands

#umount -f /nfs_apps

or

#umount -l /nfs_apps

SNMP Configuration File

To check which config files the agent is attempting to read.

Try running
snmpd -f -Le -Dread_config

linux tr command

The tr utility copies the given input to produced the output with substitution or deletion of selected characters. tr abbreviated as translate or transliterate. It takes as parameters two sets of characters, and replaces occurrences of the characters in the first set with the corresponding elements from the other set i.e. it is used to translate characters.

tr command syntax

tr [options] “set1″ “set2″
echo something | tr “set1″ “set2″
tr “set1″ “set2″ < input.txt
tr “set1″ “set2″ < input.txt > output.txt

Example

Translate the word ‘linux’ to upper-case:
$ echo ‘linux’ | tr “[:lower:]” “[:upper:]”
$ echo ‘linux’ | tr “a-z” “A-Z”
$ echo ‘I LovE linuX. one is better Than 2′ | tr “a-z” “A-Z”

How to set StickBit SUID GUID

SUID – [ Set User ID ]

SUID bit is set for files ( mainly for scripts ).
The SUID permission makes a script to run as the user who is the owner of the script, rather than the user who started it.

Example:
If a1 is the owner of the script and b2 tries to run the same script, the script runs with the ownership of a1.
If the root user wants to give permissions for some scripts to run by different users, he can set the SUID bit for that particular script.
So if any user on the system starts that script, it will run under the root ownership.

Note:
root user much be very carefull with this.

SGID – [ Set Group ID ]

If a file is SGID, it will run with the privileges of the files group owner, instead of the privileges of the person running the program.
This permission set also can make a similar impact. Here the script runs under the groups ownership.

You can also set SGID for directories.
Consider you have given 2777 permission for a directory. Any files created by any users under this directory will come as follows.

Example:
-rw-rw-r– 1 b2 a1 0 Jun 11 17:30 1.txt

In the above example you can see that the owner of the file 1.txt is b2 and the group owner is a1.
So both b2 and a1 will have access to the file 1.txt.
Now lets make this more intresting and complicated.
Create a directory “test”. Chmod it to 2777. Add sticky bit to it.

Example:
mkdir test
chmod 2777 test
chmod +t test

ls -al test
drwxrwsrwt 2 a1 a1 4096 Jun 13 2008 test

From the above permission set you can understand that SGID and sticky bit is set for the folder “test”.
Now any user can create files under the test directory.

Example:
drwxrwsrwt 2 a1 a1 4096 Jun 13 2008 .
-rw-rw-r– 1 b2 a1 0 Jun 11 17:30 1.txt
-rw-rw-r– 1 c3 a1 0 Jun 11 17:30 2.txt
-rw-rw-r– 1 d4 a1 0 Jun 11 17:30 3.txt

So all the a1 user has access to all the files under the test directory. He can edit, rename or remove the file.
b2 user has access to 1.txt only, c3 has access to 2.txt only…

If sticky bit was not set for the test directory, any user can delete any files from the test directory, since the test directory has 777 permissions.
But now it not possible.

Example:
If d4 tries to remove 1.txt
rm -f 1.txt
rm: cannot remove `1.txt’: Operation not permitted