Exit code 137 on a backup Post: 23566

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

All about exit code

Hi, I am working on Solaris 8 and the "intro" man page says, "Upon termination, each command returns two bytes of status, one supplied by the system and given the cause for termination, and (in the case of 'normal' termination) one supplied by the program. The former byte is 0 for normal...

2. UNIX for Dummies Questions & Answers

Where can I find a list of exit codes? (Exit code 64)

I'm receiving an exit code 64 in our batch scheduler (BMC product control-m) executing a PERL script on UX-HP. Can you tell me where I can find a list of exit codes and their meaning. I'm assuming the exit code is from the Unix operating system not PERL.

3. Shell Programming and Scripting

error code 137 and error code 35072

Hi while trying to run few scripts /afs/ae.ge.com/informatica/ardw/dev/bin/cdw_ar_update_recvbal.sh this script contains the below data load_dir=/afs/ae.ge.com/informatica/ardw/dev/data prog_dir=/afs/ae.ge.com/informatica/ardw/dev/bin ctl_dir=/afs/ae.ge.com/informatica/ardw/dev/ctl...

4. Shell Programming and Scripting

rsync backup mode(--backup) Are there any options to remove backup folders on successful deployment?

Hi Everyone, we are running rsync with --backup mode, Are there any rsync options to remove backup folders on successful deployment? Thanks in adv.

5. UNIX for Dummies Questions & Answers

UNIX exit code 11

We have a batch Unix process that runs during the day and it is getting an exit code 11 from Unix. It finishes a sqlplus step and gets the exit code 11 before it starts the next step. This used to happen once a year and now is happening more often (but not every time the process runs). We have...

6. Shell Programming and Scripting

Exit code

can anyone tell what the exit status - 137 belongs in unix shell scripting.

LEARN ABOUT REDHAT

cron

CRON(8) 						      System Manager's Manual							   CRON(8)

NAME

       cron - daemon to execute scheduled commands (Vixie Cron)

SYNOPSIS

       cron

DESCRIPTION

       Cron should be started from /etc/rc or /etc/rc.local.  It will return immediately, so you don't need to start it with '&'.

       Cron searches /var/spool/cron for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into memory.  Cron
       also searches for /etc/crontab and the files in the /etc/cron.d/ directory, which are in a different format (see  crontab(5)).	Cron  then
       wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current minute.  When execut-
       ing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable in the crontab,	if
       such exists).

       Additionally,  cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab) has changed, and if it has,
       cron will then examine the modtime on all crontabs and reload those which have changed.	Thus cron need not be restarted whenever a crontab
       file is modified.  Note that the Crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.

SEE ALSO

       crontab(1), crontab(5)

AUTHOR

       Paul Vixie <paul@vix.com>

4th Berkeley Distribution					 20 December 1993							   CRON(8)