Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: exit status of command in a pipe line
Top Forums UNIX for Dummies Questions & Answers exit status of command in a pipe line Post 47545 by topcat8 on Thursday 12th of February 2004 09:36:04 AM
Old 02-12-2004
exit status of command in a pipe line
Hi,

I am trying to test the exit status of the cleartool lsvtree statement below, but it doesn't seem to be working due to the tail pipe, which it is testing instead. Is there a way around this without adding a tonne of new code?
Code:
   cleartool lsvtree $testlocation/$exe_name | tail -15
   #exit out if not file not in dir
   if [ $? -ne 0 ]; then
          echo "Error: File not in test or application area"
          exit 1
   fi

Thanks
Cath

added code tags for readability --oombera
Last edited by oombera; 02-18-2004 at 12:29 PM..
 

10 More Discussions You Might Find Interesting

1. Programming

How to find the exit status of last command in Unix?

Hi, I want to find the exit status of the last executed command in C Shell. Tried $? but getting the error Variable syntax...$? does not seem to work in C shell.. is there any other command in C shell to find the exit status of last command? Thanks in advance, raju (1 Reply)
Discussion started by: rajugp1
1 Replies

2. UNIX for Dummies Questions & Answers

how to find the exit status for the last executed command

I am executing a find command in my script i.e find $2 -type f -name '*.gif' -mtime +$1 -exec rm {} \; how do i check that this command is executed properly.. i would lke t trap the errror and display my error message kinly help.. this is an urgent issue. (1 Reply)
Discussion started by: vijay.amirthraj
1 Replies

3. Shell Programming and Scripting

Getting the exit status of a remote command

Hi to everyone. How can I get the exit status from a remote command executed with rexec? :eek: machine A has RedHat Linux 9 and the remote machine B has SCO UNIX. Code: rexec -l user -p password host sh /u/files/scripts/seq_cal.sh 2006 08 I want the exit status returned by... (1 Reply)
Discussion started by: zoonalex
1 Replies

4. Shell Programming and Scripting

How to get exit code in a pipe-lined command?

I have a question about how to get the exit code of the first command when it appears in a pipe-lined command. For example, I have the following script: grep abc dddd | tee -a log if ] then echo "ERROR!" fi In the above script, ] is supposed to test the exit code of "grep abc... (3 Replies)
Discussion started by: pankai
3 Replies

5. UNIX for Dummies Questions & Answers

Move Command and exit status problem

Hi All, I am using the following code to move files from one folder to another on the remote server: ssh username@server <<EOF cd source_dir find . -type f -name "*.txt" |xargs -n1000 -i{} mv {} dest_dir if then send mail indicating error otherwise echo "success" fi EOF ... (1 Reply)
Discussion started by: visingha
1 Replies

6. HP-UX

Logins command exit status is 236 not 0

I have noticed that on version 11.23 I get exit status 236 from the following command: logins -oxl root ; echo $? > 236 However on 11.31 I get the expected code 0 logins -oxl root ; echo $? > 0 The output is correct for both versions and contains no error data. Can anyone explain... (2 Replies)
Discussion started by: parkea2
2 Replies

7. UNIX for Advanced & Expert Users

Equivalents of tee command to find exit status of command

Hi, Want to log the output of command & check the exit status to find whether it succeeded or failed. > ls abc ls: abc: No such file or directory > echo $? 1 > ls abc 2>&1 | tee log ls: abc: No such file or directory > echo $? 0 Tee commands changes my exit status to be always... (7 Replies)
Discussion started by: vibhor_agarwali
7 Replies

8. Shell Programming and Scripting

Check the exit status in a pipe call

Guys, I have a problem :confused: and I need some help: I've to process many huge zip files. I'd code an application that receive the data from a pipe, so I can simple unzip the data and send it (via pipe) to my app. Something like that: gzip -dc <file> | app The problem is: How can I... (7 Replies)
Discussion started by: Rkolbe
7 Replies

9. UNIX for Dummies Questions & Answers

Exit Status Of Find Command

Hello All, I am trying to capture the exit status of find command and want to delete the files only when it is successful. But it is always returning me as success even if the pattern of that file doesn't exist in the current directory. please help, checked manual page but couldn't able to figure... (6 Replies)
Discussion started by: Ariean
6 Replies

10. Shell Programming and Scripting

Exit Status of Command

Hi All, I am doing an export and import (datapump) of 4 schema. I know we can do an export of 4 schema in one command. But just want to know how to check the exit status if i do the export/import of 4 schema in different commands in background. Please suggest. Thanks, Mani (1 Reply)
Discussion started by: pvmanikandan
1 Replies

LEARN ABOUT DEBIAN

runsv

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

NAME

       runsv - starts and monitors a service and optionally an appendant log service

SYNOPSIS

       runsv service

DESCRIPTION

       service must be a directory.

       runsv  switches to the directory service and starts ./run.  If ./run exits and ./finish exists, runsv starts ./finish.  If ./finish doesn't
       exist or ./finish exits, runsv restarts ./run.

       If ./run or ./finish exit immediately, runsv waits a second before starting ./finish or restarting ./run.

       Two arguments are given to ./finish.  The first one is ./run's exit code, or -1 if ./run didn't exit normally.  The second one is the least
       significant  byte  of  the exit status as determined by waitpid(2); for instance it is 0 if ./run exited normally, and the signal number if
       ./run was terminated by a signal.  If runsv cannot start ./run for some reason, the exit code is 111 and the status is 0.

       If the file service/down exists, runsv does not start ./run immediately.  The control interface (see below) can be used to start  the  ser-
       vice and to give other commands to runsv.

       If  the	directory  service/log	exists,  runsv	creates  a pipe, redirects service/run's and service/finish's standard output to the pipe,
       switches to the directory service/log and starts ./run (and ./finish) exactly as described above for the service directory.   The  standard
       input of the log service is redirected to read from the pipe.

       runsv  maintains  status  information in a binary format (compatible to the daemontools' supervise program) in service/supervise/status and
       service/log/supervise/status, and in a human-readable format in service/supervise/stat, service/log/supervise/stat,  service/supervise/pid,
       service/log/supervise/pid.

CONTROL

       The  named pipes service/supervise/control, and (optionally) service/log/supervise/control are provided to give commands to runsv.  You can
       use sv(8) to control the service or just write one of the following characters to the named pipe:

       u      Up.  If the service is not running, start it.  If the service stops, restart it.

       d      Down.  If the service is running, send it a TERM signal, and then a CONT signal.	If ./run  exits,  start  ./finish  if  it  exists.
	      After it stops, do not restart service.

       o      Once.  If the service is not running, start it.  Do not restart it if it stops.

       p      Pause.  If the service is running, send it a STOP signal.

       c      Continue.  If the service is running, send it a CONT signal.

       h      Hangup.  If the service is running, send it a HUP signal.

       a      Alarm.  If the service is running, send it a ALRM signal.

       i      Interrupt.  If the service is running, send it a INT signal.

       q      Quit.  If the service is running, send it a QUIT signal.

       1      User-defined 1.  If the service is running, send it a USR1 signal.

       2      User-defined 2.  If the service is running, send it a USR2 signal.

       t      Terminate.  If the service is running, send it a TERM signal.

       k      Kill.  If the service is running, send it a KILL signal.

       x      Exit.   If  the  service	is running, send it a TERM signal, and then a CONT signal.  Do not restart the service.  If the service is
	      down, and no log service exists, runsv exits.  If the service is down and a log service exists, runsv closes the standard  input	of
	      the log service, and waits for it to terminate.  If the log service is down, runsv exits.  This command is ignored if it is given to
	      service/log/supervise/control.

       Example: to send a TERM signal to the socklog-unix service, either do
	 # sv term /etc/service/socklog-unix
	or
	 # printf t >/etc/service/socklog-unix/supervise/control

       printf(1) usually blocks if no runsv process is running in the service directory.

CUSTOMIZE CONTROL

       For each control character c sent to the control pipe, runsv first checks if service/control/c exists and is executable.  If so, it  starts
       service/control/c  and waits for it to terminate, before interpreting the command.  If the program exits with return code 0, runsv refrains
       from sending the service the corresponding signal.  The command o is always considered as command u.  On command d first  service/control/t
       is  checked,  and then service/control/d.  On command x first service/control/t is checked, and then service/control/x.	The control of the
       optional log service cannot be customized.

SIGNALS

       If runsv receives a TERM signal, it acts as if the character x was written to the control pipe.

EXIT CODES

       runsv exits 111 on an error on startup or if another runsv is running in service.

       runsv exits 0 if it was told to exit.

SEE ALSO

       sv(8), chpst(8), svlogd(8), runit(8), runit-init(8), runsvdir(8), runsvchdir(8), utmpset(8)

       http://smarden.org/runit/

AUTHOR

       Gerrit Pape <pape@smarden.org>

																	  runsv(8)
All times are GMT -4. The time now is 10:09 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy