Every 15 minutes my script does:
So most of the time I don't want an email every 15 minutes that the script ran and logged to the db, just if the temp is high.
Sorry, but that's no script. That is a plan after which to write a script, at best. Most probably your script bears Cron Problem Number One, but that is just a wild guess as long as you post rubbish instead of your failing script.
Does any one knows a work around for the crontab bug when connecting using ssh to a Solaris 8 system?
When you submit a crontab job through a ssh session, the job will not be executed, SunSolve has reported no fixing patches? (3 Replies)
Hi
..first post !
I have a Unix v445 using solaris 10. I've trolled through various web pages but can't find exactly what I'm looking for.
I have an alert log...or any messages file for that matter I need to check for certain key (error type) phrases - if I find them, they are redirected to... (11 Replies)
Hi,
I am having trouble with this script. It is suppose to send me an email when the specified tablespace is 60% full. I run it but nothing happens
FREESPACELOG=/home/oracle/scripts/bin/free_space/freespace.sql
email=bob@bob.edu
subject="PROD: Tablespace Free Space"
cmd="mailx -s... (1 Reply)
hi all,
how do i email a file in the body of an email rather than as an attachment ??
have a ksh script which i need to read a file and email as part of the body rather than an attachment.
my code is :
uuencode file.log | mailx -s "test"
but this sends file as an attachment.
... (2 Replies)
Hi there,
I'm using crontab to move some files every minute, but when crontab doesn't find these files it sends a message to the file "user_name" in the directory "var/spool/mail". Is it possible to "bypass" this problem?
Thanks in advance,
Giordano Bruno (1 Reply)
Hi there,
I'm working with two servers, one with FEDORA 6 and the other one with FEDORA 7, and if I put these lines in crontab:
MAILTO=MYADDRESS@mail.com
*/1 * * * * df -h
everything works fine on FEDORA 7 , while it doesn't work on6?!?...and I find this message in the log file:
MAIL... (2 Replies)
Hello Guru's
I'm trying to take the output of solaris top command and output to a txt file every few minutes. The issue that I'm experiencing is that I can run the following:
#!/bin/bash
#
logfile="/usr/mvf/morris/top.log"
# echo... (2 Replies)
HI,
I am using centos 6 and finding difficultly in doing 2 below things.
1. i have a user praveen i want to allow him to create cron job of his own. so i have added his user id in cron.allow but still it is not allowing him to edit(even if i have created praveen from root user) or create his... (4 Replies)
Hi All,
The following databse table maintains
VENDOR and EMAIL details.
VENOR_NAME VENDOR_EMAIL
DELL surendra@dell.com
HP rajkamal@hp.com
ACER sumathi@acer.com
NOKIA kunal@nokia.com
SONY sinu@sony.com
We have to find emaild id of a vendor based... (7 Replies)
Discussion started by: ROCK_PLSQL
7 Replies
LEARN ABOUT DEBIAN
rt-email-dashboards-4
rt-email-dashboards(8) Request Tracker Reference rt-email-dashboards(8)NAME
rt-email-dashboards - Send email dashboards
SYNOPSIS
rt-email-dashboards [options]
DESCRIPTION
This tool will send users email based on how they have subscribed to dashboards. A dashboard is a set of saved searches, the subscription
controls how often that dashboard is sent and how it's displayed.
Each subscription has an hour, and possibly day of week or day of month. These are taken to be in the user's timezone if available, UTC
otherwise.
SETUP
You'll need to have cron run this script every hour. Here's an example crontab entry to do this.
0 * * * * /usr/bin/perl /opt/rt4/local/sbin/rt-email-dashboards
This will run the script every hour on the hour. This may need some further tweaking to be run as the correct user.
OPTIONS
This tool supports a few options. Most are for debugging.
-h
--help Display this documentation
--dryrun
Figure out which dashboards would be sent, but don't actually generate or email any of them
--time SECONDS
Instead of using the current time to figure out which dashboards should be sent, use SECONDS (usually since midnight Jan 1st, 1970,
so 1192216018 would be Oct 12 19:06:58 GMT 2007).
--epoch SECONDS
Back-compat for --time SECONDS.
--all Ignore subscription frequency when considering each dashboard (should only be used with --dryrun for testing and debugging)
perl v5.14.2 2013-05-22 rt-email-dashboards(8)