pipestatus 0.5.0 (Default branch)

Tags

default, pipes, pipestatus, software releases

Special Forums News, Links, Events and Announcements Software Releases - RSS News pipestatus 0.5.0 (Default branch)

05-23-2008

Registered User

26,240, 27

Join Date: Sep 2000

Last Activity: 1 August 2008, 3:09 PM EDT

Posts: 26,240

Thanks Given: 0

Thanked 27 Times in 26 Posts

pipestatus 0.5.0 (Default branch)

pipestatus is a source file for UNIX/POSIX shellsthat provides set of functions for obtaining theexit status of every program in a pipe withoutusing non-portable extensions. Most shells, suchas BSD /bin/sh, ksh, pdksh, ash, bash, dash, mksh,and zsh are supported.License: Public DomainChanges:
"check_status_re" and therefore "runpipe_re" use"grep -E" instead of "grep" in order to simplifythe regexp that contains exit statuses of 2 ormore digits. Formally speaking, this breaksbackward compatibility. If the PIPESTATUS_VERBOSEvariable is set to a non-empty string, then thecheck_status0 and check_status_re functions printan error message to stderr.

More...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Bash ${PIPESTATUS[@]}

I'm using this form of variable setting to use the exit status of a pipeline e.g. foo=$(date|grep -i thursday)$? echo $foo echo ${PIPESTATUS} or $foo later in a script. On days other than Thursday it results in: 1 0 For some reason the PIPESTATUS array doesn't show. I'd...

2. Shell Programming and Scripting

Creating a run script, getting pipestatus from eval

Hi All, I'm new to bash so I appreciate any help. Basically I want to create a script that takes 1 argument, a string from the command line. It then executes that string emailing me the std out and std err. And lastly it checks the exit status of the job and sends me an email telling me if the...

LEARN ABOUT HPUX

pipe

pipe(2) 							System Calls Manual							   pipe(2)

NAME

       pipe() - create an interprocess channel

SYNOPSIS

DESCRIPTION

       creates	an  I/O  mechanism  called  a pipe and returns two file descriptors, fildes[0] and fildes[1].  fildes[0] is opened for reading and
       fildes[1] is opened for writing.

       A read-only file descriptor fildes[0] accesses the data written to fildes[1] on a first-in-first-out (FIFO) basis.  For details of the  I/O
       behavior of pipes see read(2) and write(2).

       By  default,  HP-UX  pipes are not STREAMS-based.  It is possible to generate the kernel so that all pipes created on a system are STREAMS-
       based.  This can only be done for HP-UX releases 10.0 and later.  STREAMS-based FIFOs (created by or are not supported on HP-UX.

       To generate a kernel that supports STREAMS-based pipes:

	 o  STREAMS/UX must be installed.

	 o  The module and the driver must be included in the file.  (When STREAMS/UX is installed, and are  automatically  added  to  the  system
	    file.)

	 o  The  tunable  parameter  (see  streampipes(5))  must  be  set  to  1  in the file.	(This is not automatically done when STREAMS/UX is
	    installed.)

	 o  The kernel must be generated and the system rebooted.  Once this is done, all pipes created by will be STREAMS-based.

       For more information, see

EXAMPLES

       The following example uses to implement the command string

RETURN VALUE

       returns one of the following values:

	      Successful completion.

	      Failure.
		     is set to indicate the error.

ERRORS

       sets to one of the following error values if the corresponding condition is true.

       or more file descriptors are currently open.

       The system file table is full.

       The file system lacks sufficient space to create the pipe.

       Could not allocate resources for both Stream heads
		      (STREAMS-based pipes only).

SEE ALSO

       sh(1), read(2), write(2), popen(3S), privileges(5), streampipes(5), streamio(7).

STANDARDS CONFORMANCE

																	   pipe(2)

Software Releases - RSS News