Changes

* <code>.bash_logout</code> :: Executed when you log out

This file can only be modified by the root user. Affects the environment of all users, regardless of their default shell. Bash users can change their environment by modifying the <code>.bash_profile</code> or the <code>.bashrc</code> files. Different shells have different configuration files. Other configuration files such as <code>.profile</code> exist - read comments in your <code>.bash_rc</code> file to find out more

Located in the user’s home directory. These files are executed every time a user logs in or creates a new shell. Things vary depending whether the shell is interactive or not. By modifying either one of these files, each user can change his individual working environment. They can be used for the following:

* Mapping new keys on the keyboard

Many shells keep a history of recently executed command lines in a file. This history is used by users to save time, when executing same or similar commands over and over. Bash uses the up/down arrow keys. Use the Ctrl+r to search by keyword. Bash stores it’s history in the <code>.bash_history</code> file

A way to create “shortcuts” or temporary commands in UNIX. Stored in memory, while the user is logged in. Usually found in the <code>.bash_profile</code>. Syntax:

<code>alias clearfile=”cat /dev/null &gt;”</code>

Shell variables a classified in 2 groups:

Variables can be read/write or read-only. Name of a variable can be any sequence of letters and numbers, but it must not start with a number.

Shell environment variables shape the working environment whenever you are logged in. Common shell variables include:

{|

| primary prompt

|-

| present working directory

|-

| absolute path to user’s home

|-

| list of directories where executables are

|-

| name of the host

|-

| name of the user logged in

|-

| current shell

|}

The <code>set</code> command will display all available variables

* <code>PATH</code> is an environment variable present in Unix/Linux operating systems, listing directories where executable programs are located

* Use <code>./</code> prefix or modify the <code>PATH</code> as needed

Syntax: <code>name=value</code>

* If no variable name is supplied a list of defined read only variables will be displayed

<code>variable=</code>

Read-only variables cannot be removed, you must log out for them to be cleared.

Whenever you wish to read a variable (its contents), use the variable name preceded by a dollar sign ($). This is commonly called ''variable substitution''.

Alice

</source>

= Introduction to Shell Scripting =

fi

</source>

= <code>test</code> Command =

{|

| file exists

|-

| file exists and is a directory

|-

| file exists and has a size greater than zero

|-

| file exists and write permission is granted

|}