11-16-2010
Thanks
Tried running this command on anather UNIX machine
ls -t /PROCESSED/* | tail +9 | xargs rm
I get the following error message
usage:rm [-fiRr] file ...
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi All
I am trying to run a .sh file from cron but its not performing its intended purpose, though the same sh file works fine when triggered manually.Following mail I recieve when it tries to run the script.
*********************************************************
To: wlsdev05
Subject:... (16 Replies)
Discussion started by: pankajkrmishra
16 Replies
2. Shell Programming and Scripting
Hi All ,
We have few scripts which uses common environment/path setting variables.
Now instead of putting classpath , framework,java_home ..... etc. in all the script, can we make a file with all common settings which can be envoked by the scripts while running. If yes , say setting file is... (3 Replies)
Discussion started by: pankajkrmishra
3 Replies
3. UNIX for Dummies Questions & Answers
Regarding Cron job,
i want to execute a scriptevery 4 days once irrespective of a week or a month.
Is it possible?Any help (2 Replies)
Discussion started by: santho
2 Replies
4. UNIX for Dummies Questions & Answers
can anybody explain the usage of CRON for adding a cron job. please provide an example also for better understanding !!!
Thanks (1 Reply)
Discussion started by: skyineyes
1 Replies
5. Solaris
I run cron in solaris 10 zone. One cron job which syncing files to nfs mounted on container, creates after finishing another cron proccess(/usr/sbin/cron), and after 100 existing cron proccesses next cron job will not start. It's too weird for me, I'm not able to solve this problem. Theoretically... (3 Replies)
Discussion started by: ron76
3 Replies
6. UNIX for Advanced & Expert Users
Hello,
Can anyone help me how to set any script as cron job. I have gone through all threads but not able to get the details. Appreciate your help.
I need to set test.pl to run on every Tuesday by 6am in the morning.
I do not the cron file which is defined.
Please help me out.
... (3 Replies)
Discussion started by: jam_prasanna
3 Replies
7. Solaris
Hi ,
I have removed a cron for particular user , but cron job seems to be running even after the cron entry is removed. The purpose of the cron was to sendmail to user ( it uses mailx utility )
I have restarted cron and sendmail service still user is getting mail alerts from the cron job. And... (4 Replies)
Discussion started by: chidori
4 Replies
8. Shell Programming and Scripting
Hi
I have a requirement to write a shell script,that will check the all commented job in cron job.Please help !! (2 Replies)
Discussion started by: netdbaind
2 Replies
9. UNIX for Dummies Questions & Answers
How to schedule a cron job to run every other Monday.
Thanks in advance. (2 Replies)
Discussion started by: ITDev01
2 Replies
10. Shell Programming and Scripting
Hi,
1)
If some job supposed to run on 1st of every month at 7 AM
In cron job when we have a blackout on the 1st ( i.e when 1st falls on a sunday ) how can we make the job run the next business day?
2) How can we run a job on 25th of every quarter 7 AM(jan,apr,jul,oct)
And if 25th... (5 Replies)
Discussion started by: System Admin 77
5 Replies
TAIL(1) BSD General Commands Manual TAIL(1)
NAME
tail -- display the last part of a file
SYNOPSIS
tail [-f | -F | -r] [-b number | -c number | -n number] [file ...]
DESCRIPTION
The tail utility displays the contents of file or, by default, its standard input, to the standard output.
The display begins at a byte, line or 512-byte block location in the input. Numbers having a leading plus (``+'') sign are relative to the
beginning of the input, for example, ``-c +2'' starts the display at the second byte of the input. Numbers having a leading minus (``-'')
sign or no explicit sign are relative to the end of the input, for example, ``-n 2'' displays the last two lines of the input. The default
starting location is ``-n 10'', or the last 10 lines of the input.
The options are as follows:
-b number
The location is number 512-byte blocks.
-c number
The location is number bytes.
-f The -f option causes tail to not stop when end of file is reached, but rather to wait for additional data to be appended to the
input. The -f option is ignored if the standard input is a pipe, but not if it is a FIFO.
-F The -F option is the same as the -f option, except that every five seconds tail will check to see if the file named on the command
line has been shortened or moved (it is considered moved if the inode or device number changes) and, if so, it will close the current
file, open the filename given, print out the entire contents, and continue to wait for more data to be appended. This option is used
to follow log files though rotation by newsyslog(8) or similar programs.
-n number
The location is number lines.
-r The -r option causes the input to be displayed in reverse order, by line. Additionally, this option changes the meaning of the -b,
-c and -n options. When the -r option is specified, these options specify the number of bytes, lines or 512-byte blocks to display,
instead of the bytes, lines or blocks from the beginning or end of the input from which to begin the display. The default for the -r
option is to display all of the input.
If more than a single file is specified, each file is preceded by a header consisting of the string ``==> XXX <=='' where ``XXX'' is the name
of the file.
The tail utility exits 0 on success, and >0 if an error occurs.
SEE ALSO
cat(1), head(1), sed(1)
STANDARDS
The tail utility is expected to be a superset of the IEEE Std 1003.2-1992 (``POSIX.2'') specification. In particular, the -b, -r and -F
options are extensions to that standard.
The historic command line syntax of tail is supported by this implementation. The only difference between this implementation and historic
versions of tail, once the command line syntax translation has been done, is that the -b, -c and -n options modify the -r option, i.e. ``-r
-c 4'' displays the last 4 characters of the last line of the input, while the historic tail (using the historic syntax ``-4cr'') would
ignore the -c option and display the last 4 lines of the input.
HISTORY
A tail command appeared in Version 7 AT&T UNIX.
BUGS
When using the -F option, tail will not detect a file truncation if, between the truncation and the next check of the file size, data written
to the file make it larger than the last known file size.
BSD
June 6, 1993 BSD