Archive for the ‘Utilities’ Category


Setting up cronjobs in Unix and Solaris

cron is a unix, solaris utility that allows tasks to be automatically run in the background at regular intervals by the cron daemon. These tasks are often termed as cron jobs in unix , solaris.
Crontab (CRON TABle) is a file which contains the schedule of cron entries to be run and at specified times.

Crontab Restrictions

You can execute crontab if your name appears in the file /usr/lib/cron/cron.allow. If that file does not exist, you can use crontab if your name does not appear in the file /usr/lib/cron/cron.deny. 
If only cron.deny exists and is empty, all users can use crontab. If neither file exists, only root user can use crontab.The allow/deny files consist of one user name per line.

Crontab Commands
crontab -e     Edit your crontab file, or create one if it doesn’t already exist.
crontab -l      Display your crontab file.
crontab -r      Remove your crontab file.
crontab -v      Display the last time you edited your crontab file. (This option is only available on a few systems.)

Crontab file
A crontab file has five fields for specifying day , date and time  followed by the command to be run at that interval.

min hr dom month dow cmd

*     *   *   *    *  command to be executed

-     -    -    -    –

|     |     |     |     |

|     |     |     |     +—– day of week (0 – 6) (Sunday=0)

|     |     |     +——- month (1 – 12)

|     |     +——— day of month (1 – 31)

|     +———– hour (0 – 23)

+————- min (0 – 59)

* in the value field above means all legal values as in braces for that column.

The value column can have a * or a list of elements separated by commas. An element is either a number in the ranges shown above or two numbers in the range separated by a hyphen (meaning an inclusive range).

     * 12 16 * Mon root cmd

Will run cmd at midday every Monday and every 16th, and will produce the

same result as both of these entries put together would:

     59 11 * * 1,2,3,4,5 root

Will run at 11:59 Monday, Tuesday, Wednesday, Thursday

and Friday,as will:

59 11 * * 1-5 root

Cron also supports ‘step’ values.A value of */2 in the dom field would mean the command runs every two daysand likewise, */5 in the hours field would mean the command runs every 5 hours.e.g.

* 12 10-16/2 * * root

is the same as:

* 12 10,12,14,16 * * root

*/15 9-17 * * * root connection.test

Will run connection.test every 15 mins between the hours or 9am and 5pm

To collect the cron execution execution log in a file :

30 18  *    *   *    rm /home/someuser/tmp/* > /home/someuser/cronlogs/clean_tmp_dir.log


cron job executing ‘’ to be ran on the LAST day of every month at 23:58 :

58 23 * * * [ `date +%d` -eq `echo \`cal\` | awk ‘{print $NF}’` ] &&



Setting Up Passwordless Connection

Secure Copy or SCP is a means of securely transferring computer files between a local and a remote host or between two remote hosts, using the Secure Shell (SSH) protocol.

The term SCP can refer to one of two related things, the SCP protocol or the SCP program.

*** use password less only if needed , making life easier then it needs to be has adverse consequences …

$ /usr/bin/ssh-keygen -t rsa

Generating public/private rsa key pair.
Enter file in which to save the key (/export/home/oracle/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /export/home/oracle/.ssh/id_rsa.
Your public key has been saved in /export/home/oracle/.ssh/
The key fingerprint is:
3e:89:0c:44:5c:09:e9:07:98:cc:6a:35:35:17:3d:dd oracle@wdlilnxsusrs01

cat >> user@hostb:~/.ssh/authorized_keys

Now you can ssh/scp from host A to host B do the same on host B to allow both servers only if needed that host B connects to host A without password.


Using SCP to copy Files

If user dvader is on a computer called, and wants to copy a file called file1.txt to a directory called somedir in his account on a computer called, he would enter:

scp file1.txt

Likewise, if he wanted to copy the entire contents of the somedir directory on back to his account, he would enter:

scp -r somedir

Similarly, if he is working on another computer, but wanted to copy a file called file1.txt from his home directory on to a directory called somedir in his account on, he would enter:



FIND Command

To look across the /bin and /var/html directory trees for filenames that contain the pattern *.htm*, you can use the following command:

find /usr /var/html -name “*.htm*” -print

Finding udump directory starting from ORACLE_BASE

find $ORACLE_BASE -name “udump” -print

Finding Directories

To find a list of the directories use can use the -type specifier.

find . -type d -print


Access,Modified,Changed Time

“-atime/-ctime/-mtime” [+|-]n

Specify selection of the files based on  three Unix timestamps: the last time a files’s “access time”, “file status” and “modification time”.  
n is time interval — an integer with optional sign. It is measured in 24-hour periods (days) or minutes counted from the current moment.

  • +n: if it has plus sing, then it means “more than n 24-hour periods (days) ago”, or older then n,
  • -n: if it has the minus sign, then it means less than n 24-hour periods (days) ago (-n), or younger than n. It’s evident that -1,  and 0 are the same and both means “today”.
  • n: If the integer n does not have sign this means exactly n 24-hour periods (days) ago, 0 means today.

find everything in your home directory modified in the last 24 hours:
                        find $HOME -mtime -1

Find everything in your home directory modified in the last seven 24-hour periods (days):
                       find $HOME -mtime -7

Find everything in your home directory that have NOT been modified in the last year:
                      find $HOME -mtime +365

To find html files that have been modified in the last seven 24-hour periods (days), I can use -mtime with the argument -7 (include the hyphen): 
                     find . -mtime -7 -name “*.html” -print

If you use the number 7 (without a hyphen), find will match only html files that were modified exactly seven 24-hour periods (days) ago:
                      find . -mtime 7 -name “*.html” -print

To find those html files that I haven’t touched for at least seven 24-hour periods (days), I use +7:
                     find . -mtime +7 -name “*.html” -print


-newer/-anewer/-cnewer baseline_file

The time of modification, access time or creation time are compared with the same timestamp in the baseline file. If file is a symbolic link and the -H option or the -L option is in effect, the modification time of the file it points to is always used.

  • -newer Modification time is compared with modification time of the basline_file True if file was modified more recently than baseline file.
  • -anewer Access time is compared with access time of basline_file . True if file was last accessed more recently than baseline file.
  • -cnewer Creation file is compared. For example: find everything in your home that has been modified more recently than “~joeuser/lastbatch.txt “:

find $HOME -newer ~joeuser/lastbatch.txt



Locates files with specified size. -size attribute lets you specify how big the files should be to match. You can specify your size in kilobytes and optionally also use + or – to specify size greater than or less than specified argument. For example:

find /home -name “*.txt” -size 100k
find /home -name “*.txt” -size +100k
find /home -name “*.txt” -size -100k


Using Find with OR options

$ find . \( -name a.out -o -name ‘*.o’ -o -name ‘core’ \) -exec rm {} \;

File masks identifying the file types to be removed are located between the parentheses; each file mask is preceded by -name. This list can be extended to include any temporary file types you can come up with that need to be cleaned off the system. In the course of compiling and linking code, programmers and their tools generate file types like those shown in the example: a.out, *.o, and core. Other users have similar commonly generated temporary files and can edit the command accordingly, using file masks like *.tmp, *.junk, and so on. You might also find it useful to put the command into a script called clean, which you can execute whenever you need to clean a directory.


$ find $LOGDIR -type d -mtime +0 -exec compress -r {} \;

$ find $LOGDIR -type d -mtime +5 -exec rm -f {} \;

The first command runs all the directories (-type d) found in the $LOGDIR directory wherein a file’s data has been modified within the last 24 hours (-mtime +0) and compresses them (compress -r {}) to save disk space. The second command deletes them (rm -f {}) if they are more than a work-week old (-mtime +5), to increase the free space on the disk.


To list all zero-length files, use this command:

find . -empty -exec ls {} \;

FIND Logical Expressions

To negate a condition (logical NOT) . NOT should be specified with a backslash before exclamation point ( \! ). For example

find . \! -name “*.gz” -exec gzip {} \;

\( expression \)  —  “escaped parentheses” to specify any composite condition. For example

find / -type f \( -perm -4000 -o -perm -2000 \) -exec ls -l {} \;

If you wanted to find a list of files that have been modified in the last 24 hours and which has a permission of 777, you would execute the following command:

find . -perm 777  -mtime 0 -print
Which is the same as:
find . -perm 777 -a -mtime 0 -a -print


Link of Checking Age of Files with FIND command


Touch Command

Touch command change only mtime. For example if you need to change the date to Jun 21, 2008 9AM to example.txt, then you can go (-t parameter in touch has format [[CC]YY]MMDDhhmm[.SS]):

    touch -t 200907210900 example.txt


To list files in /u/bill that were last read from 2 to 6 minutes ago:

    find /u/bill -amin +2 -amin -6


Comparing TimeStamps

There are two ways to list files in /usr modified after February 1 of the current year. One uses ‘-newermt’:

     find /usr -newermt “Feb 1”

The other way of doing this works on the versions of find before 4.3.3:

     touch -t 02010000 /tmp/stamp$$
     find /usr -newer /tmp/stamp$$
     rm -f /tmp/stamp$$


Using -exec and XARGS with FIND

The find command is commonly used to remove core files that are more than a few 24-hour periods (days) old. These core files are copies of the actual memory image of a running program when the program dies unexpectedly. They can be huge, so occasionally trimming them is wise:

find . -name core -ctime +4 -exec /bin/rm -f {} \;


For example often one needs to find files containing a specific pattern in multiple directories one can use an exec option in find (please note that you should use the -l flag for grep so that grep specifies the matched filenames):

find . -type f -exec grep -li ‘/bin/ksh’ {} \;

Find how many directories are in a path (counts current directory)
# find . -type d -exec basename {} \; wc -l

Find how many files are in a path
# find . -type f -exec basename {} \; wc -l

Find files that were modified less than 7 days ago and archive
# find . -type f -mtime -7 xargs tar -cvf `date ‘+%d%m%Y’_archive.tar`

More examples on this link