Exit code 137 on a backup Post: 24693

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 LINUX

warn.conf

warn.conf(4)							   File Formats 						      warn.conf(4)

NAME

       warn.conf - Kerberos warning configuration file

SYNOPSIS

       /etc/krb5/warn.conf

DESCRIPTION

       The  warn.conf file contains configuration information specifying how users will be warned by the ktkt_warnd daemon about ticket expiration
       on a Kerberos client. Credential expiration warnings are sent, by means of syslog, to auth.notice. All other warning messages are  sent	to
       daemon.notice.

       Each  Kerberos  client host must have a warn.conf file in order for users on that host to get Kerberos warnings from the client. Entries in
       the warn.conf file must have the following format:

       principal syslog | terminal | mail time [email_address]

       principal       Specifies the principal name to be warned. The asterisk (*) wildcard can be used to specify groups of principals.

       syslog	       Sends the warnings to the system's syslog. Depending on the /etc/syslog.conf  file,  syslog  entries  are  written  to  the
		       /var/adm/messages file and/or displayed on the terminal.

       terminal        Sends the warnings to display on the terminal.

       mail	       Sends the warnings as email to the address specified by email_address.

       time	       Specifies  how  much  time before the TGT expires when a warning should be sent. The default time value is seconds, but you
		       can specify h (hours) and m (minutes) after the number to specify other time values.

       email_address   Specifies the email address at which to send the warnings. This field must be specified only with the mail field.

EXAMPLES

       Example 1: Specifying warnings

       The following warn.conf entry

       * syslog 5m

       specifies that warnings will be sent to the syslog five minutes before the expiration of the TGT for all principals. The form of  the  mes-
       sage is:

       jdb@ACME.COM: your kerberos credentials expire in 5 minutes

FILES

       /usr/lib/krb5/ktkt_warnd        Kerberos warning daemon

SEE ALSO

       ktkt_warnd(1M), syslog.conf(4), SEAM(5)

SunOS 5.10							    22 Apr 2003 						      warn.conf(4)