Exit code 137 on a backup Post: 302179475

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 OSF1

killall

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

NAME

       killall - Terminates all processes started by the user, except the calling process

SYNOPSIS

       /usr/sbin/killall [- | [-]signal_name | -signal_number]

       /usr/sbin/killall -l

FLAGS

       The  hyphen  character (without an argument) sends a SIGTERM signal initially and then sends a SIGKILL signal to all processes that survive
       for 30 seconds after receipt of the first signal.  This gives processes that catch the SIGTERM signal an opportunity to clean up.  A signal
       name, optionally preceded by a hyphen, sends the specified signal to processes.	The hyphen character (with a signal number argument) sends
       the specified signal, either a name, stripped of the SIG prefix (such as KILL), or a number (such as  9).   For	information  about  signal
       names and numbers, see the signal() system call.

       In  the System V habitat, the optional signal number does not have to be preceded with a hyphen (-).  Lists signal names in numerical order
       (as given in the /usr/include/signal.h file), stripped of the common SIG prefix.

DESCRIPTION

       This command provides a convenient means of killing all processes created by the shell that you control.  When started  by  the	superuser,
       the killall command kills all processes that can be terminated, except those processes that started it, the kernel processes, and processes
       0 and 1 (init).

   Security Configuration
       This command is modified in all security configurations of the system.

EXAMPLES

       To stop all background processes that have started, enter: killall This sends all background processes signal  9  (the  kill  signal,  also
       called  SIGKILL).   To  stop  all  background processes, giving them a chance to clean up, enter: killall - This sends signal 15 (SIGTERM),
       waits 30 seconds, and then sends signal 9 (SIGKILL).  To send a specific signal to the background processes, enter: killall -2  This  sends
       signal  2 (SIGINT) to the background processes.	To list the signal names in numerical order, stripped of the SIG prefix, enter: killall -l
       This displays a list of signals, which may vary from system to system.

FILES

       Specifies the command path

RELATED INFORMATION

       Calls: kill(2), sigaction(2), signal(2) delim off

																	killall(8)