how can I reschedule a job if it fails Post: 302279317

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

killing unix job after the job process completes

Hi, Thanks in advance. i need to kill a unix background running job after that job process completes. i can kill a job by giving the following unix command kill -9 processid how to kill the job after the current process run gets completed ? Appreciate your valuable help. ...

2. Solaris

killing a unix job after the job process gets completed

3. UNIX for Dummies Questions & Answers

How to insert child job under a box job?

I have this box job and it contains only one job under it which is to load a file. I want to insert a "File Watcher", "Copy File" to it? Have no clue how to do that...any help plzzz...

4. Shell Programming and Scripting

Cron job fails, but works fine from command line

I have a very basic script that essentially sends a log file, via FTP, to a backup server. My cron entry to run this every night is: 55 23 * * * /usr/bin/archive_logs The script runs perfectly when executed manually, and actually worked via cron for about three weeks. However, it mysteriously...

5. UNIX for Dummies Questions & Answers

Script ran by job scheduler fails from the 15th to the 20th of the month

Hi, I have a script that finds the application logs from the previous day and sends it to another server via ftp. The code is something like this: yest_date=`TZ=CST+24 date "+%b %d"` logdir=/app/logs logs=app*.log tmpdir=/tmp cd $logdir for i in `ls -1 $logs` do chkstr=`ls -1l $i | grep...

6. UNIX for Dummies Questions & Answers

If FTP cron job fails to connect = quit

Im having a problem with my ftp CRON jobs. I have another related (but not the same question in shell scripting). My FTP CRON jobs connect to a server and drop some files off, if for some reason it cannot connect to the server (timesout/password wrong etc) instead of stopping, it tries again...

7. Shell Programming and Scripting

Script to Start a Job after finding the Old job completed

Hi Experts, I need a script advice to schedule 12 jobs ( SAS Codes execute back ground ). Algorithem: 1. Script checks first job. 2. Finds first job is done; invoke second job. 3. finds second job is done; invoke third job. .. Request you to please assist.

8. Shell Programming and Scripting

autosys job configuration for job failure.

We need to configure autosys that when a job fails continously for 3 times, we need to call another job. Is this possible in Autosys, or can anyone advice on the alternative.

9. UNIX for Advanced & Expert Users

Cron job fails every now and then.

I added a shell script to cron that executes every 5-15 minutes. It's used to monitor multiple environments, so it has to ssh to each machine to check the status of that machine. Sometimes, I may have more than one instance of this script running at the same time. So, here's my problem. I've...

10. Shell Programming and Scripting

Cron job fails with [DataDirect][ODBC lib] Connection not open error

Hi, When run the script directly...it executes as expected. But when put it in crontab the job fails with this error: Connection not open 08003: Connection not open Unable to connect to the database... how come it is not able to connect when cron job fires?... Do I need to...

LEARN ABOUT DEBIAN

dspam_maintenance

dspam_maintenance(1)						   User Commands					      dspam_maintenance(1)

NAME

       dspam_maintenance - remove old signatures and unimportant tokens from the DSPAM storage backend

SYNOPSIS

       dspam_maintenance [--profile=PROFILE] [--logdays=no_of_days] [--signatures=no_of_days] [--neutral=no_of_days] [--unused=no_of_days]
       [--hapaxes=no_of_days] [--hits1s=no_of_days] [--hits1i=no_of_days] [--without-sql-purge] [--with-sql-automatization] [--with-sql-autoup-
       date] [--purgescriptdir=directory] [--with-all-drivers] [--verbose]

DESCRIPTION

       dspam_maintenance  is  used to remove old signatures/tokens and unimportant tokens from the DSPAM storage backend and purge old log entries
       in user and system logs.

       This script can be called from the command line or run from within cron. Either add a line in your crontab  or  add  this  script  in  your
       cron.{hourly,daily,weekly,monthly}.  Running this script every hour might not be the best idea but it's your decision if you want to do so.

OPTIONS

       --profile=PROFILE

	      Specify a storage profile from dspam.conf. The storage profile selected will be used for all database connectivity.

	      NOTE: See dspam.conf for more information.

       --logdays=no_of_days

	      All log entries older than no_of_days days will be removed.

	      NOTE: Default is 31 days. (for more info: man dspam_logrotate)

       --signatures=no_of_days

	      All signatures older than no_of_daysdays will be removed.

	      NOTE:  Default  value  is  set by the PurgeSignatures option in dspam.conf, if this option is not set, the default value is 14 days.
	      This option is only used for the Hash driver.

       --neutral=no_of_days

	      Deletes all tokens from the target users database whose probability is between 0.35 and 0.65 (fairly neutral, useless data).

	      NOTE: Default value is set by the PurgeNeutral option in dspam.conf, if this option is not set, the default value is 90 days.

       --unused=no_of_days

	      Remove stale tokens which have not been used for a long period of time.

	      NOTE: Default value is set by the PurgeUnused option in dspam.conf, if this option is not set, the default value is 90 days.

       --hapaxes=no_of_days

	      Remove tokens with a total hit count below 5 (which will be assigned a hapaxial value by DSPAM).

	      NOTE: Default value is set by the PurgeHapaxes option in dspam.conf, if this option is not set, the default value is 30 days.

       --hits1s=no_of_days

	      Remove tokens with a single SPAM hit.

	      NOTE: Default value is set by the PurgeHits1S option in dspam.conf, if this option is not set, the default value is 15 days.

       --hits1i=no_of_days

	      Remove tokens with a single INNOCENT hit.

	      NOTE: Default value is set by the PurgeHits1I option in dspam.conf, if this option is not set, the default value is 15 days.

       --without-sql-purge

	      Do not use SQL based purging. Only run dspam_clean.

	      NOTE: Default is off (aka: use SQL based purging).

       --with-sql-optimization

	      Run VACUUM (for PostgreSQL/SQLite) and/or OPTIMIZE (for MySQL).

	      NOTE: Default is off (aka: do not use optimizations).

       --with-sql-autoupdate

	      Run SQL based purging with purge day values passed to dspam_maintenance.

	      NOTE: Default is off (aka: do not attempt to modify SQL instructions).

       --purgescriptdir=directory

	      Space separated list of directories where to search for SQL files used for the SQL based purging.

       --with-all-drivers

	      Process all installed storage drivers (not just the active driver).

	      NOTE: Default is true (aka: process all installed drivers).

       --verbose

	      Verbose output while running maintenance script.

EXIT VALUE

       0      Operation was successful.
       other  Operation resulted in an error. Run the script with --verbose to get more information about error.

COPYRIGHT

       Copyright (C) 2002-2010 DSPAM Project
       All rights reserved.

       For more information, see http://dspam.sourceforge.net.

SEE ALSO

       dspam(1), dspam_admin(1), dspam_clean(1), dspam_crc(1), dspam_dump(1), dspam_logrotate(1), dspam_merge(1), dspam_stats(1), dspam_train(1)

dspam_maintenance						   Apr 26, 2010 					      dspam_maintenance(1)