08-15-2002
Why not just use the full path to microsec in the cronjob?
That way, you don't have to worry about pathing for the individual user and if the cronjob is ever moved to another user, you are still good to go. And if another admin has to work with this cronjob, the placement of microsec is obvious.
10 More Discussions You Might Find Interesting
1. Solaris
When I list whats in cron -l its fine but when I try to -e edit it...it returns a number 309 can't you not edit cron this way with solaris 10? I can do it fine in sol 8 and 9.
export EDITOR="vi" is set in my profile
I am using BASH
$ sudo crontab -l
Password:
#ident "@(#)root ... (5 Replies)
Discussion started by: kingdbag
5 Replies
2. Red Hat
Hello,
Having and issue with a job scheduled in cron. The script:
#!/bin/bash
2
3 # Example shell script which can be added to roots cron job to check the
4 # Embedded Satellite disk space usage. If any table is over 90% usage, send
5 # a notice to the default email address... (2 Replies)
Discussion started by: mgb
2 Replies
3. Shell Programming and Scripting
Hi Guys.,,
This thing is driving me crazy..
I have this script which runs perfectly fine. If it is not able to connect to database it will drop a mail which it does when i ran it manually.
But when i am running it from crontab, the script is not sending mail to me but to my id(login id)... (0 Replies)
Discussion started by: mac4rfree
0 Replies
4. Red Hat
Hey all! I'm working on setting up a script to run with cron. I have thus far been unable to get it to successfully complete. I'm hoping you gurus can lend me a hand.
This is my crontab, the transfer script works fine the backup will not. The backup however does work when I execute it from the... (11 Replies)
Discussion started by: spiffyville
11 Replies
5. Shell Programming and Scripting
Hi Gurus,
I need to run a script every saturday at 7:05 PM. Below command is working in x86_64.
05 19 * * 6 /apps/informatica/scripts/inf_rest.ksh
However when I tried in HP-UX it is giving the below error.
crontab: error on previous line; unexpected character found in line.
Please... (4 Replies)
Discussion started by: svajhala
4 Replies
6. UNIX for Advanced & Expert Users
I have written a custom cron. This cron executes a rake task every 5 minutes. I also log the trace of this execution in a file locally on my server. The whole process seems to execute seamlessly every 5 minutes, but then it seems to log it in /var/log/syslog. I investigated on the syslog and found... (0 Replies)
Discussion started by: manjunath.nm89
0 Replies
7. UNIX for Dummies Questions & Answers
I have written a custom cron. This cron executes a rake task every 5 minutes. I also log the trace of this execution in a file locally on my server. The whole process seems to execute seamlessly every 5 minutes, but then it seems to log it in /var/log/syslog. I investigated on the syslog and found... (0 Replies)
Discussion started by: manjunath.nm89
0 Replies
8. Ubuntu
I have written a custom cron. This cron executes a rake task every 5 minutes. I also log the trace of this execution in a file locally on my server. The whole process seems to execute seamlessly every 5 minutes, but then it seems to log it in /var/log/syslog. I investigated on the syslog and found... (3 Replies)
Discussion started by: manjunath.nm89
3 Replies
9. Solaris
Hello, I am running Solaris 8. I have set a cron job that runs every couple hours. If I run the script manually, it runs just fine (logged in as root). The cron however will not run. It is producing an rc=1 error. Any thoughts would be appreciated. Thanks (4 Replies)
Discussion started by: jkmtm
4 Replies
10. Shell Programming and Scripting
i have written a script to sftp yesterday's logs from another server as below:
cd /export/home/abc/xyz/tt
d=`gdate -d'yesterday' +%Y%m%d`
sftp abc@XXX.XX.XX.XX<<EOF
cd /yyy/logs/archive
mget abc.log.$d*
EOF
cd /export/home/abc/xyz/scripts
nohup ./ss.sh PROD &
it is working fine... (2 Replies)
Discussion started by: ssk250
2 Replies
LEARN ABOUT DEBIAN
logtool
logtool(1) General Commands Manual logtool(1)
NAME
logtool - parse and filter syslog files
SYNOPSIS
(stdout) | logtool -[args]
Logtool is a command line program that will parse logfiles into a more palatable format. It will take anything resembling a syslog or mul-
tilog file, as well as unformatted ASCII, and crunch it into one of the following formats for your viewing pleasure:
ANSI (colorized for easy "at a glance" viewing)
ASCII (e-mail reports/term's w/o color)
CSV (spreadsheet/database imports)
HTML (for generating web pages)
RAW (for no good reason)
OPTIONS
-o [ ANSI | ASCII | CSV | HTML | RAW ]
Allows you to specify the output format to be one of the following: ANSI (default), ASCII, CSV, HTML, RAW. Options are not case sen-
sitive (ie: -o CSV and -o csv should yield the same results)
-t [ long | short ]
Allows you to specify the time display format to be one of the following: (Long [default]) Mon Dy HH:MM:SS or (Short) HH:MM
-b Causes logtool to beep on RED events (ANSI output only). This is usefull when you want to monitor a logfile on an ongoing basis, and
wish to have your terminal beep whenever something out of the ordinary happens.
-s Causes logtool to not display the syslog "source" field
-p Causes logtool to not display the "program" field
-c [/path/config.file]
Allows you to specify a config file other than the default /etc/logtool/logtool.conf
-i [/path/includefile]
Allows you to specify an alterate file containing regex's for inclusion [default=/etc/logtool/include]
-e [/path/excludefile]
Allows you to specify an alternate file containing regex's for exclusion [default=/etc/logtool/exclude]
-n Causes logtool to skip any attempts to resolve IP->Hostname by the various modules (handy when your DNS is down temporairly).
-v Set logtool to operate in verbose mode (does nothing currently)
-V Causes logtool to print it's version information and exit
-h Display the help message
SUGGESTED USAGE(S)
As a 'live' logfile monitoring tool:
tail -f /var/log/messages | logtool -o ANSI -b
To generate colorized webpages of logfiles:
cat /var/log/messages | logtool -o HTML > /home/httpd/html/logs/messages.html
To generate reports via a cronjob:
retail /var/log/messages | logtool -o ASCII | mail -s "Daily report" someuser@somedomain.ext
CONFIG FILE
/etc/logtool/logtool.conf
The config file should be commented to the point of being self-documenting, so we will not comment very extensively on it here. Suffice to
say, this is the place where you should configure 99% of your runtime options for logtool. You may also have a collection of different
default configurations, and select amongst them by the '-c' option of logtool.
AVAILABILITY
Logtool is known to compile/run on all UNIX flavors using a 2.95.x GNU C Compiler, the GNU Make utility, and a proper ANSI C library (glibc
is recommended, but not required). Specific reports of success include FreeBSD, OpenBSD, Solaris, SunOS, AIX, SCO, and of course, any
known flavor of Linux (including at least 2 embedded system variants).
SEE ALSO
regex(7) for help with constructing regular expressions for the include/exclude/colors files. If you find no regex manual on your system,
try 'apropos regex' and see what you get, or as a last ditch, 'man grep' should at least point you in the right direction.
You can also find a somewhat better bit of documentation in the textfile 'logtool.txt' (usually in the /usr/doc/, /usr/share/doc/ or simi-
lar tree on most Linux distributions). If you don't know where to look, you can probably find it by typing 'locate logtool.txt' at the
command line.
AUTHOR
A.L.Lambert <al@xjack.org>
LOCAL logtool(1)