06-30-2003
You can try the following in the cron job (as long as the cron job isn't sending it's output to taper.log):
mailx -s"taper log" youruser@yourcompany < `tail -8 /yourdir/taper.log`
Edited: Perderabo is correct - I don't know what I was thinking!
Last edited by RTM; 06-30-2003 at 02:05 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Ok i looked through quite a few posts but could not find what i was looking for so forgive me if this post can be found elese where...
I would like to use a command like tail view what users are doing in the system i have quite a few dba's that come come to my office and do work on the system... (7 Replies)
Discussion started by: bbutler3295
7 Replies
2. Shell Programming and Scripting
Not sure why this does not work in bash:
tail -f err.log |&
-bash: syntax error near unexpected token `&'
I am attempting to continuously read a file that is being updated by doing a "tail -f" on the file and piping the output to stdin which can then be read by the next shell command
Thnx (4 Replies)
Discussion started by: anuramdas
4 Replies
3. UNIX for Dummies Questions & Answers
Hi ,
I have Continuous updating log file. I want to continuously scan that file using "tail -f " and execute a shell command like "date" command when that particular keyword is detected .
I am using awk to acheive it but not suceeded so far. However when I use "cat" instead of tail -f this... (3 Replies)
Discussion started by: scott_tiger
3 Replies
4. Shell Programming and Scripting
Hi All,
How I will read the output of the tail -F command in perl.
I have text file with below contains
file1.txt
1
2
3
4
$running=1;
sub openLog($)
{
(my $log) = @_; (1 Reply)
Discussion started by: pravin27
1 Replies
5. UNIX for Advanced & Expert Users
Hi Dears,
I am using AWK script to monitor some log files. My awk will get the input from the output of tail -f LOGFILE. (tail -f LOGFILE | myawkanalyzer)
My doubt is, How can I notify, if I didn't get any output from the tail -f command. i.e) Log file stuck for some reason. I want to display... (1 Reply)
Discussion started by: sharif
1 Replies
6. Shell Programming and Scripting
The below code works to tail client.log file. but I want to copy the output into an external file /home/tail.txt
Can anyone please help.
#!/opt/bin/perl -w
open my $pipe, "-|", "/usr/bin/tail", "/var/log/client.log" or die "could not start tail on /var/log/client.log : $!";
print while... (2 Replies)
Discussion started by: sureshcisco
2 Replies
7. Shell Programming and Scripting
Hello;
Am trying to correct the formatting of tail output over ssh.
Using the following code:
echo "" > $FILE
for BOX in $SERVERS
do
echo "Processing on $BOX" |tee -a $FILE
echo "===============================" >> $FILE
sudo ssh $BOX 'TERMINAL="vt100" /usr/bin/sh -s' <... (2 Replies)
Discussion started by: delphys
2 Replies
8. Shell Programming and Scripting
Hello,
I need to tail -f a file output stream and I need to get only lines that contains "get" and "point" in the same line. It doesn't matter the order.
Then I need only the text BEFORE "point".
I have to count each line and perform other serveral actions after this has performed 3 times.... (9 Replies)
Discussion started by: Kibou
9 Replies
9. UNIX for Dummies Questions & Answers
hi guys,
I perform a sort of monitoring. I have a server running and with
tail -f | grep "Searchstring"I monitor the log-file for recent specific entries. This is ok and works fine.
Now, in addition I want to have my search results not posted into the shell but into a file. I tried:
tail... (3 Replies)
Discussion started by: LaUs3r
3 Replies
10. Shell Programming and Scripting
Redirecting the tail output fails when log rotation happens even though i have used -F. But when i tail and see the output on terminal this does not happen. Note i have also used & to execute this statement in background.
Suppose if i want to tail a file /opt/SAMPLE.txt and redirect its output... (1 Reply)
Discussion started by: CN1
1 Replies
cron(1M) System Administration Commands cron(1M)
NAME
cron - clock daemon
SYNOPSIS
/usr/sbin/cron
DESCRIPTION
cron starts a process that executes commands at specified dates and times.
You can specify regularly scheduled commands to cron according to instructions found in crontab files in the directory
/var/spool/cron/crontabs. Users can submit their own crontab file using the crontab(1) command. Commands which are to be executed only once
can be submitted using the at(1) command.
cron only examines crontab or at command files during its own process initialization phase and when the crontab or at command is run. This
reduces the overhead of checking for new or changed files at regularly scheduled intervals.
As cron never exits, it should be executed only once. This is done routinely by way of the svc:/system/cron:default service. The file
/etc/cron.d/FIFO file is used as a lock file to prevent the execution of more than one instance of cron.
cron captures the output of the job's stdout and stderr streams, and, if it is not empty, mails the output to the user. If the job does not
produce output, no mail is sent to the user. An exception is if the job is an at(1) job and the -m option was specified when the job was
submitted.
cron and at jobs are not executed if your account is locked. Jobs and processses execute. The shadow(4) file defines which accounts are not
locked and will have their jobs and processes executed.
Setting cron Jobs Across Timezones
The timezone of the cron daemon sets the system-wide timezone for cron entries. This, in turn, is by set by default system-wide using
/etc/default/init.
If some form of daylight savings or summer/winter time is in effect, then jobs scheduled during the switchover period could be executed
once, twice, or not at all.
Setting cron Defaults
To keep a log of all actions taken by cron, you must specify CRONLOG=YES in the /etc/default/cron file. If you specify CRONLOG=NO, no log-
ging is done. Keeping the log is a user configurable option since cron usually creates huge log files.
You can specify the PATH for user cron jobs by using PATH= in /etc/default/cron. You can set the PATH for root cron jobs using SUPATH= in
/etc/default/cron. Carefully consider the security implications of setting PATH and SUPATH.
Example /etc/default/cron file:
CRONLOG=YES
PATH=/usr/bin:/usr/ucb:
This example enables logging and sets the default PATH used by non-root jobs to /usr/bin:/usr/ucb:. Root jobs continue to use
/usr/sbin:/usr/bin.
The cron log file is periodically rotated by logadm(1M).
FILES
/etc/cron.d Main cron directory
/etc/cron.d/FIFO Lock file
/etc/default/cron cron default settings file
/var/cron/log cron history information
/var/spool/cron Spool area
/etc/cron.d/queuedefs Queue description file for at, batch, and cron
/etc/logadm.conf Configuration file for logadm
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
svcs(1), at(1), crontab(1), sh(1), logadm(1M), svcadm(1M), queuedefs(4), shadow(4), attributes(5), smf(5)
NOTES
The cron service is managed by the service management facility, smf(5), under the service identifier:
svc:/system/cron:default
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
DIAGNOSTICS
A history of all actions taken by cron is stored in /var/cron/log and possibly in /var/cron/olog.
SunOS 5.10 5 Aug 2004 cron(1M)