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
logcheck
Logcheck(8) System Manager's Manual Logcheck(8)
NAME
logcheck -- program to scan system logs for interesting lines
SYNOPSIS
logcheck [OPTIONS]
DESCRIPTION
The logcheck program helps spot problems and security violations in your logfiles automatically and will send the results to you periodi-
cally in an e-mail. By default logcheck runs as an hourly cronjob just off the hour and after every reboot.
logcheck supports three level of filtering: "paranoid" is for high-security machines running as few services as possible. Don't use it if
you can't handle its verbose messages. "server" is the default and contains rules for many different daemons. "workstation" is for shel-
tered machines and filters most of the messages. The ignore rules work in additive manner. "paranoid" rules are also included at level
"server". "workstation" level includes both "paranoid" and "server" rules.
The messages reported are sorted into three layers, system events, security events and attack alerts. The verbosity of system events is
controlled by which level you choose, paranoid, server or workstation. However, security events and attack alerts are not affected by
this.
EXAMPLES
logcheck can be invoked directly thanks to su(8) or sudo(8), which change the user ID. The following example checks the logfiles without
updating the offset and outputs everything to STDOUT.
sudo -u logcheck logcheck -o -t
OPTIONS
A summary of options is included below.
-c CFG Overrule default configuration file.
-d Debug mode.
-h Show usage information.
-H Use this hostname string in the subject of logcheck mail.
-l LOG Run logfile through logcheck.
-L CFG Overrule default logfiles list.
-m Mail report to recipient.
-o STDOUT mode, not sending mail.
-p Set the report level to "paranoid".
-r DIR Overrule default rules directory.
-R Adds "Reboot:" to the email subject line.
-s Set the report level to "server".
-S DIR Overrule default state directory.
-t Testing mode does not update offset.
-T Do not remove the TMPDIR.
-u Enable syslog-summary.
-v Print current version.
-w Set the report level to "workstation".
FILES
/etc/logcheck/logcheck.conf is the main configuration file.
/etc/logcheck/logcheck.logfiles is the list of files to monitor.
/usr/share/doc/logcheck-database/README.logcheck-database.gz for hints on how to write, test and maintain rules.
EXIT STATUS
0 upon success; 1 upon failure
SEE ALSO
logtail(8)
AUTHOR
logcheck is developed by Debian logcheck Team at alioth: http://alioth.debian.org/projects/logcheck/.
This manual page was written by Jon Middleton.
Logcheck(8)